diff options
| author |   Nícolas F. R. A. Prado <nfraprado@collabora.com> | 2022-01-12 14:41:42 -0500 |
|---|---|---|
| committer |   Shuah Khan <skhan@linuxfoundation.org> | 2022-01-25 13:16:01 -0700 |
| commit | f034cc1301e7d83d4ec428dd6b8ffb57ca446efb (patch) | |
| tree | 23d037ea4830aabca8940def0a8c4d7fba81108b /tools/testing/selftests/rtc/settings | |
| parent | Linux 5.17-rc1 (diff) | |
| download | wireguard-linux-f034cc1301e7d83d4ec428dd6b8ffb57ca446efb.tar.xz wireguard-linux-f034cc1301e7d83d4ec428dd6b8ffb57ca446efb.zip | |
selftests: rtc: Increase test timeout so that all tests run
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>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/testing/selftests/rtc/settings')
| -rw-r--r-- | tools/testing/selftests/rtc/settings | 2 |
1 files changed, 1 insertions, 1 deletions
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 |