From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: Shuah Khan <shuah@kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-rtc@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v2] selftests: rtc: Increase test timeout so that all tests run
Date: Wed, 12 Jan 2022 21:22:08 +0100 [thread overview]
Message-ID: <Yd84cDlW9+f7wQxq@piout.net> (raw)
In-Reply-To: <20220112194142.3276385-1-nfraprado@collabora.com>
On 12/01/2022 14:41:42-0500, Nícolas F. R. A. Prado wrote:
> The timeout setting for the rtc kselftest is currently 90 seconds. This
> setting is used by the kselftest runner to stop running a test if it
> takes longer than the assigned value.
>
> However, two of the test cases inside rtc set alarms. These alarms are
> set to the next beginning of the minute, so each of these test cases may
> take up to, in the worst case, 60 seconds.
>
> In order to allow for all test cases in rtc to run, even in the worst
> case, when using the kselftest runner, the timeout value should be
> increased to at least 120. Set it to 180, so there's some additional
> slack.
>
> Correct operation can be tested by running the following command right
> after the start of a minute (low second count), and checking that all
> test cases run:
>
> ./run_kselftest.sh -c rtc
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> ---
>
> Changes in v2:
> - Expanded commit message to make the issue, and how to test the fix, clearer
>
> v1: https://lore.kernel.org/all/20220112165359.3206047-1-nfraprado@collabora.com/
>
> tools/testing/selftests/rtc/settings | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/rtc/settings b/tools/testing/selftests/rtc/settings
> index ba4d85f74cd6..a953c96aa16e 100644
> --- a/tools/testing/selftests/rtc/settings
> +++ b/tools/testing/selftests/rtc/settings
> @@ -1 +1 @@
> -timeout=90
> +timeout=180
> --
> 2.34.1
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-01-12 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 19:41 Nícolas F. R. A. Prado
2022-01-12 20:22 ` Alexandre Belloni [this message]
2022-01-12 23:51 ` Shuah Khan
2022-01-25 20:52 ` Shuah Khan
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=Yd84cDlW9+f7wQxq@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=nfraprado@collabora.com \
--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®