Steven Rostedt 4651920e0a 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>

2011-03-08 09:52:58 -05:00

..

firewire

tools/firewire: nosy-dump: increment program version

2010-07-27 11:04:12 +02:00

perf

perf timechart: Fix max number of cpus

2011-02-28 08:56:15 +01:00

power/x86

tools: turbostat: style updates

2011-02-10 23:58:13 -05:00

slub

slub: move slabinfo.c to tools/slub/slabinfo.c

2010-11-06 09:04:32 +02:00

testing/ktest

ktest: Fix bug where the test would not end after failure

2011-03-08 09:52:58 -05:00

usb

USB: testusb: testusb compatibility with FunctionFS gadget

2010-05-20 13:21:43 -07:00

virtio

tools/virtio: virtio_test tool

2010-12-09 16:00:22 +02:00