aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/testing/selftests/rtc/settings
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2019-09-19 11:06:44 -0700
committerShuah Khan <skhan@linuxfoundation.org>2019-10-01 13:33:28 -0600
commit852c8cbf34d3b3130a05c38064dd98614f97d3a8 (patch)
tree8222cc49a8994be03006e4ae53f1cea8d942ea30 /tools/testing/selftests/rtc/settings
parentkselftest: exclude failed TARGETS from runlist (diff)
downloadwireguard-linux-852c8cbf34d3b3130a05c38064dd98614f97d3a8.tar.xz
wireguard-linux-852c8cbf34d3b3130a05c38064dd98614f97d3a8.zip
selftests/kselftest/runner.sh: Add 45 second timeout per test
Commit a745f7af3cbd ("selftests/harness: Add 30 second timeout per test") solves the problem of kselftest_harness.h-using binary tests possibly hanging forever. However, scripts and other binaries can still hang 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 field is "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 <keescook@chromium.org> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/testing/selftests/rtc/settings')
-rw-r--r--tools/testing/selftests/rtc/settings1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/testing/selftests/rtc/settings b/tools/testing/selftests/rtc/settings
new file mode 100644
index 000000000000..ba4d85f74cd6
--- /dev/null
+++ b/tools/testing/selftests/rtc/settings
@@ -0,0 +1 @@
+timeout=90