path: root/tools/testing/ktest/sample.conf
diff options
authorSteven Rostedt <srostedt@redhat.com>2011-03-08 09:26:31 -0500
committerSteven Rostedt <rostedt@goodmis.org>2011-03-08 09:52:58 -0500
commitc23dca7cd28eb1bf90053ce4ba30d65d22d2a81e (patch)
tree3c782d80130cb5921911e105a57491afc1af332c /tools/testing/ktest/sample.conf
parentc960bb9f59c0ed2aded535222cfe461ec6c22c95 (diff)
ktest: Add BISECT_SKIP
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>
Diffstat (limited to 'tools/testing/ktest/sample.conf')
1 files changed, 9 insertions, 0 deletions
diff --git a/tools/testing/ktest/sample.conf b/tools/testing/ktest/sample.conf
index af82ac28977..4c46b7ef8e4 100644
--- a/tools/testing/ktest/sample.conf
+++ b/tools/testing/ktest/sample.conf
@@ -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