aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/testing/ktest
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2020-07-01 10:28:23 -0400
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2020-07-01 10:28:23 -0400
commit2f059db0b8313f8964ac917394e7425d966a6884 (patch)
tree8e1748ad5673f7bc14660dcdd92ca119ef0c343d /tools/testing/ktest
parentktest.pl: Have config-bisect save each config used in the bisect (diff)
downloadwireguard-linux-2f059db0b8313f8964ac917394e7425d966a6884.tar.xz
wireguard-linux-2f059db0b8313f8964ac917394e7425d966a6884.zip
ktest.pl: Always show log file location if defined even on success
If a log file is defined and the test were to error, a print statement is made that shows the user where the log file is to examine it further. But this is not done if the test were to succeed. I find it annoying that it does not show where the log file is on success, as I run several different tests that place their log files in various locations, and even though the test pass, there's things I want to look at in the log file (like warnings). It is much easier to find where the log file is, if it is displayed at the end of a test. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/testing/ktest')
-rwxr-xr-xtools/testing/ktest/ktest.pl4
1 files changed, 4 insertions, 0 deletions
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 5f6f88911f5c..5d5cf3e1e81a 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -4441,6 +4441,10 @@ if ($opt{"POWEROFF_ON_SUCCESS"}) {
}
+if (defined($opt{"LOG_FILE"})) {
+ print "\n See $opt{LOG_FILE} for the record of results.\n";
+}
+
doprint "\n $successes of $opt{NUM_TESTS} tests were successful\n\n";
if ($email_when_finished) {