commit | d832d743385dd5e735660951aa9d7d36a6a4176a | [log] [tgz] |
---|---|---|
author | Steven Rostedt (Red Hat) <rostedt@goodmis.org> | Tue Oct 07 16:34:25 2014 -0400 |
committer | Steven Rostedt <rostedt@goodmis.org> | Tue Oct 07 16:34:25 2014 -0400 |
tree | 19d28a395d71ac95715c95416914e7cca324de88 | |
parent | 995bc4314071db148222497875be32d1eb73726d [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>