Changes in settings

2aaa36e9 - selftests/rtc: continuously read RTC in a loop for 30s

Sat, 19 Feb 2022 07:27:13 +0000

selftests/rtc: continuously read RTC in a loop for 30sSome problems with reading the RTC time may happen rarely, for examplewhile the RTC is updating. So read the RTC many times to catch theseproblems. For example, a previous attempt for mycommit ea6fa4961aab ("rtc: mc146818-lib: fix RTC presence check")was incorrect and would have triggered this selftest.To avoid the risk of damaging the hardware, wait 11ms before consecutivereads.In rtc_time_to_timestamp I copied values manually instead of casting -just to be on the safe side. The 11ms wait period was chosen so that it isnot a divisor of 1000ms.Signed-off-by: Mateusz Jończyk Cc: Alessandro Zummo Cc: Alexandre Belloni Cc: Shuah Khan Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/rtc/settings

f034cc13 - selftests: rtc: Increase test timeout so that all tests run

Wed, 12 Jan 2022 19:41:42 +0000

selftests: rtc: Increase test timeout so that all tests runThe timeout setting for the rtc kselftest is currently 90 seconds. Thissetting is used by the kselftest runner to stop running a test if ittakes longer than the assigned value.However, two of the test cases inside rtc set alarms. These alarms areset to the next beginning of the minute, so each of these test cases maytake up to, in the worst case, 60 seconds.In order to allow for all test cases in rtc to run, even in the worstcase, when using the kselftest runner, the timeout value should beincreased to at least 120. Set it to 180, so there's some additionalslack.Correct operation can be tested by running the following command rightafter the start of a minute (low second count), and checking that alltest cases run: ./run_kselftest.sh -c rtcSigned-off-by: Nícolas F. R. A. Prado Acked-by: Alexandre Belloni Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/rtc/settings

852c8cbf - selftests/kselftest/runner.sh: Add 45 second timeout per test

Thu, 19 Sep 2019 18:06:44 +0000

selftests/kselftest/runner.sh: Add 45 second timeout per testCommit a745f7af3cbd ("selftests/harness: Add 30 second timeout pertest") solves the problem of kselftest_harness.h-using binary testspossibly hanging forever. However, scripts and other binaries can stillhang forever. This adds a global timeout to each test script run.To make this configurable (e.g. as needed in the "rtc" test case),include a new per-test-directory "settings" file (similar to "config")that can contain kselftest-specific settings. The first recognized fieldis "timeout".Additionally, this splits the reporting for timeouts into a specific"TIMEOUT" not-ok (and adds exit code reporting in the remaining case).Signed-off-by: Kees Cook Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/rtc/settings