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>
This commit is contained in:
Steven Rostedt 2011-03-08 09:40:31 -05:00 committed by Steven Rostedt
parent 3410f6fd5e
commit 4651920e0a
1 changed files with 1 additions and 1 deletions

View File

@ -804,7 +804,7 @@ sub monitor {
}
if ($full_line =~ /call trace:/i) {
if (!$skip_call_trace) {
if (!$bug && !$skip_call_trace) {
$bug = 1;
$failure_start = time;
}