projects / linux.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 995bc43) | patch
ktest: Don't bother with bisect good or bad on replay
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>
Tue, 7 Oct 2014 20:34:25 +0000 (16:34 -0400)
committerSteven Rostedt <rostedt@goodmis.org>
Tue, 7 Oct 2014 20:34:25 +0000 (16:34 -0400)
commitd832d743385dd5e735660951aa9d7d36a6a4176a
tree19d28a395d71ac95715c95416914e7cca324de88tree | snapshot
parent995bc4314071db148222497875be32d1eb73726dcommit | diff
ktest: Don't bother with bisect good or bad on replay

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>
tools/testing/ktest/ktest.pl diff | blob | history
ep93xx device tree rework repo: git://git.maquefel.me/linux.git