Kernel/linux-next
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git synced 2025-01-13 09:20:17 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

ktest: Don't bother with bisect good or bad on replay

Browse Source 
If git bisect reply is being used in the bisect tests, don't bother
doing the git bisect good or git bisect bad calls. The git bisect
reply will override them anyway, and that's called immediately
after the other two. Going the git bisect (good|bad) is just a
waste of time.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
This commit is contained in:
Steven Rostedt (Red Hat) 2014-10-07 16:34:25 -04:00 committed by Steven Rostedt
parent 995bc43140
commit d832d74338
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
tools/testing/ktest/ktest.pl
View File

@ -2736,15 +2736,17 @@ sub bisect {
run_command "git bisect start$start_files" or run_command "git bisect start$start_files" or
dodie "could not start bisect"; dodie "could not start bisect";
if (defined($replay)) {
run_command "git bisect replay $replay" or
dodie "failed to run replay";
} else {
run_command "git bisect good $good" or run_command "git bisect good $good" or
dodie "could not set bisect good to $good"; dodie "could not set bisect good to $good";
run_git_bisect "git bisect bad $bad" or run_git_bisect "git bisect bad $bad" or
dodie "could not set bisect bad to $bad"; dodie "could not set bisect bad to $bad";
if (defined($replay)) {
run_command "git bisect replay $replay" or
dodie "failed to run replay";
} }
if (defined($start)) { if (defined($start)) {