diff options
author | Steven Rostedt <srostedt@redhat.com> | 2011-03-08 09:40:31 -0500 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2011-03-08 09:52:58 -0500 |
commit | 4651920e0ac7a596c1123a8efdcc2f6d2249deb3 (patch) | |
tree | 69eb8da9da385e9b0e08794befe30bb7ffe8d8b0 /scripts | |
parent | 3410f6fd5e3e96de4b557a62b7a2fbf19d74b1cd (diff) |
ktest: Fix bug where the test would not end after failure
The config STOP_AFTER_FAILURE is the number of seconds to continue
the test when a failure is detected. This lets the monitor record
more data to the logs and console that may be helpful in solving
the bug that was found.
But the test had a bug. If the failure caused multiple
"Call Trace" stack dumps, the start time to compare the
STOP_AFTER_FAILURE would constantly be reset. Only update the start
time at the first "Call Trace" instance.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions