summaryrefslogtreecommitdiffstats
path: root/tools/testing/ktest/ktest.pl
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2011-03-07 13:21:00 -0500
committerSteven Rostedt <rostedt@goodmis.org>2011-03-08 09:52:58 -0500
commit10abf118f090b9a70ea05296a981fa27196dc7c6 (patch)
tree6bcc35f3f41aeaf616a20c459081fed5ac21440c /tools/testing/ktest/ktest.pl
parentf80802cb1fbd7f441dd1d04db77d314adb7ccb37 (diff)
downloadtalos-op-linux-10abf118f090b9a70ea05296a981fa27196dc7c6.tar.gz
talos-op-linux-10abf118f090b9a70ea05296a981fa27196dc7c6.zip
ktest: Start failure timeout on panic too
Currently we just look for a Call Trace to start the time out when to reboot the box. But if the kernel panics and does not show a Call Trace, the test will not reboot the box after the specified timeout. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'tools/testing/ktest/ktest.pl')
-rwxr-xr-xtools/testing/ktest/ktest.pl1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 3e3615a7d968..6620fe4b364f 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -820,6 +820,7 @@ sub monitor {
}
if ($full_line =~ /Kernel panic -/) {
+ $failure_start = time;
$bug = 1;
}
OpenPOWER on IntegriCloud