sugar/linux
1
0
Fork 0
Code Activity

ktest: Add BISECT_SKIP

Browse Source 
If a during a git bisect, ktest fails on something other than
what it is testing (if BISECT_TYPE is test but it fails on build),
if BISECT_SKIP is set, then it will do a "git bisect skip" instead
of just failing the bisect and letting the user find a good commit
to test.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
This commit is contained in:
Steven Rostedt
2011-03-08 09:26:31 -05:00
committed by Steven Rostedt
parent c960bb9f59
commit c23dca7cd2
2 changed files with 37 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -519,6 +519,15 @@
# git bisect good, git bisect bad, and running the git bisect replay
# if the BISECT_REPLAY is set.
#
# BISECT_SKIP = 1 (optional, default 0)
#
# If BISECT_TYPE is set to test but the build fails, ktest will
# simply fail the test and end their. You could use BISECT_REPLAY
# and BISECT_START to resume after you found a new starting point,
# or you could set BISECT_SKIP to 1. If BISECT_SKIP is set to 1,
# when something other than the BISECT_TYPE fails, ktest.pl will
# run "git bisect skip" and try again.
#
# BISECT_REVERSE = 1 (optional, default 0)
#
# In those strange instances where it was broken forever