From: Steven Rostedt <srostedt@redhat.com>
Date: Tue, 8 Mar 2011 14:40:31 +0000 (-0500)
Subject: ktest: Fix bug where the test would not end after failure
X-Git-Tag: v2.6.39-rc1~396^2~2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4651920e0ac7a596c1123a8efdcc2f6d2249deb3;p=profile%2Fivi%2Fkernel-x86-ivi.git

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>
---

diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 65c5c55..125ab94 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -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;
 	    }