aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/testing/ktest
diff options
context:
space:
mode:
authorChris J Arges <chris.j.arges@canonical.com>2014-08-27 13:26:53 -0500
committerSteven Rostedt <rostedt@goodmis.org>2014-09-19 20:12:52 -0400
commitfee9d3e61d04422628a3d22ed5eb8370dcef259b (patch)
tree195f34d75a12e29c936b793e8af8f4e66460a296 /tools/testing/ktest
parentktest: Add PATCHCHECK_CHERRY (diff)
downloadwireguard-linux-fee9d3e61d04422628a3d22ed5eb8370dcef259b.tar.xz
wireguard-linux-fee9d3e61d04422628a3d22ed5eb8370dcef259b.zip
ktest: add ability to skip during BISECT_MANUAL
When doing a manual bisect, a build can fail or a test can be inconclusive. In these cases it would be helpful to be able to skip the test entirely. Link: http://lkml.kernel.org/r/1409164021-2136-1-git-send-email-chris.j.arges@canonical.com Reviewed-by: Satoru Takeuchi <satoru.takeuchi@gmail.com> Signed-off-by: Chris J Arges <chris.j.arges@canonical.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'tools/testing/ktest')
-rwxr-xr-xtools/testing/ktest/ktest.pl6
1 files changed, 4 insertions, 2 deletions
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 3b7a180d9c0d..085452fa045b 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -2338,15 +2338,17 @@ sub success {
sub answer_bisect {
for (;;) {
- doprint "Pass or fail? [p/f]";
+ doprint "Pass, fail, or skip? [p/f/s]";
my $ans = <STDIN>;
chomp $ans;
if ($ans eq "p" || $ans eq "P") {
return 1;
} elsif ($ans eq "f" || $ans eq "F") {
return 0;
+ } elsif ($ans eq "s" || $ans eq "S") {
+ return -1;
} else {
- print "Please answer 'P' or 'F'\n";
+ print "Please answer 'p', 'f', or 's'\n";
}
}
}