sugar/linux
1
0
Fork 0
Code Activity

ktest: Added force stop after success and failure

Browse Source 
Added the options STOP_AFTER_SUCCESS and STOP_AFTER_FAILURE to
allow the user to give a time (in seconds) to stop the monitor
after a stack trace or login has been detected. Sometimes the
kernel constantly prints out to the console and this may cause
the test to run indefinitely.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
This commit is contained in:
Steven Rostedt
2010-11-09 12:55:40 -05:00
committed by Steven Rostedt
parent cccae1a62a
commit 1c8a617a27
2 changed files with 44 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
tools/testing/ktest/sample.conf
View File

@@ -294,6 +294,18 @@
# (default "login:")
#SUCCESS_LINE = login:
# In case the console constantly fills the screen, having
# a specified time to stop the test after success is recommended.
# (in seconds)
# (default 10)
#STOP_AFTER_SUCCESS = 10
# In case the console constantly fills the screen, having
# a specified time to stop the test after failure is recommended.
# (in seconds)
# (default 60)
#STOP_AFTER_FAILURE = 60
# Stop testing if a build fails. If set, the script will end if
# a failure is detected, otherwise it will save off the .config,
# dmesg and bootlog in a directory called