Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Laura Nao <laura.nao@collabora.com>
To: laura.nao@collabora.com
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, shuah@kernel.org
Subject: Re: [PATCH 0/2] Modify the watchdog selftest for execution with
Date: Thu,  6 Jun 2024 11:57:14 +0200	[thread overview]
Message-ID: <20240606095714.397658-1-laura.nao@collabora.com> (raw)
In-Reply-To: <20240506111359.224579-1-laura.nao@collabora.com>

Hi Shuah,

On 5/6/24 13:13, Laura Nao wrote:
> The watchdog selftest script supports various parameters for testing
> different IOCTLs. The watchdog ping functionality is validated by
> starting
> a loop where the watchdog device is periodically pet, which can only
> be
> stopped by the user interrupting the script.
> 
> This results in a timeout when running this test using the kselftest
> runner
> with no non-oneshot parameters (or no parameters at all):
> 
>   TAP version 13
>   1..1
>   # timeout set to 45
>   # selftests: watchdog: watchdog-test
>   # Watchdog Ticking Away!
>   # .............................................#
>   not ok 1 selftests: watchdog: watchdog-test # TIMEOUT 45 seconds
> 
> To address this issue, the first patch in this series limits the loop
> to 5
> iterations by default and adds support for a new '-c' option to
> customize
> the number of pings as required.
> 
> The second patch conforms the test output to the KTAP format.
> 

Gentle ping - any thoughts on this series? It would simplify running the
watchdog kselftest in CI environments by leveraging the runner.

Thanks!

Laura

  parent reply	other threads:[~2024-06-06  9:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 11:13 [PATCH 0/2] Modify the watchdog selftest for execution with kselftest runner Laura Nao
2024-05-06 11:13 ` [PATCH 1/2] selftests/watchdog: limit ping loop and allow configuring the number of pings Laura Nao
2024-06-27 18:48   ` Shuah Khan
2024-07-03 14:48     ` Laura Nao
2024-07-03 23:10       ` Shuah Khan
2024-05-06 11:13 ` [PATCH 2/2] selftests/watchdog: convert the test output to KTAP format Laura Nao
2024-06-27 18:41   ` Shuah Khan
2024-07-03 14:49     ` Laura Nao
2024-06-06  9:57 ` Laura Nao [this message]
2024-06-06 23:03   ` [PATCH 0/2] Modify the watchdog selftest for execution with Shuah Khan
2024-06-07  9:53     ` Laura Nao
2024-06-07 21:07       ` Shuah Khan
2024-06-18 13:40         ` Laura Nao
2024-06-21 21:08           ` Shuah Khan
2024-06-24 15:00             ` Laura Nao

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=20240606095714.397658-1-laura.nao@collabora.com \
    --to=laura.nao@collabora.com \
    --cc=kernel@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