From: Shuah Khan <skhan@linuxfoundation.org>
To: Laura Nao <laura.nao@collabora.com>, shuah@kernel.org
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Modify the watchdog selftest for execution in non-interactive environments
Date: Thu, 5 Dec 2024 11:37:53 -0700 [thread overview]
Message-ID: <a0816bb6-fc78-433a-9cb4-7c16f06d3675@linuxfoundation.org> (raw)
In-Reply-To: <20241119150127.152830-1-laura.nao@collabora.com>
On 11/19/24 08:01, Laura Nao wrote:
> This series is a follow-up to v1[1], aimed at making the watchdog selftest
> more suitable for CI environments. Currently, in non-interactive setups,
> the watchdog kselftest can only run with oneshot parameters, preventing the
> testing of the WDIOC_KEEPALIVE ioctl since the ping loop is only
> interrupted by SIGINT.
>
> The first patch adds a new -c option to limit the number of watchdog pings,
> allowing the test to be optionally finite. The second patch updates the
> test output to conform to KTAP.
>
> The default behavior remains unchanged: without the -c option, the
> keep_alive() loop continues indefinitely until interrupted by SIGINT.
>
> [1] https://lore.kernel.org/all/20240506111359.224579-1-laura.nao@collabora.com/
>
> Changes in v2:
> - The keep_alive() loop remains infinite by default
> - Introduced keep_alive_res variable to track the WDIOC_KEEPALIVE ioctl return code for user reporting
>
> Laura Nao (2):
> selftests/watchdog: add -c option to limit the ping loop
> selftests/watchdog: convert the test output to KTAP format
I think we discussed this conversion before and I still don't see
the need for this especially this patch converts every single
print() into ktap which isn't necessary.
>
> .../selftests/watchdog/watchdog-test.c | 169 +++++++++++-------
> 1 file changed, 103 insertions(+), 66 deletions(-)
>
These don't apply on 6.13 or 6.12 - rebase and resend after
making changes to address comments on individual patches.
thanks,
-- Shuah
prev parent reply other threads:[~2024-12-05 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 15:01 Laura Nao
2024-11-19 15:01 ` [PATCH v2 1/2] selftests/watchdog: add -c option to limit the ping loop Laura Nao
2024-12-06 2:48 ` Shuah Khan
2024-11-19 15:01 ` [PATCH v2 2/2] selftests/watchdog: convert the test output to KTAP format Laura Nao
2024-12-05 18:34 ` Shuah Khan
2024-12-05 18:37 ` Shuah Khan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a0816bb6-fc78-433a-9cb4-7c16f06d3675@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=laura.nao@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®