bisect-kit: bisector 'run --force'
This CL changed the behavior of bisector 'run' subcommand slightly.
Original behavior:
If bisect failed (verify failed or skip too many times), the result
is not saved and terminated.
So users can resume by just calling 'run' directly. However, there is
a problem when integrated with diagnose_cros_autotest.py. Assume the
culprit is inside chromeos tree, so android bisector and chrome
bisector would fail as expected. When diagnose_cros_autotest.py
resume, it will waste time to run android and chrome bisector again.
New behavior:
Bisect result will always be saved even the result is failure. If
users want to resume failed session, they can do 'run --force', which
switch and eval at least one more time even if last run failed.
BUG=None
TEST=When bisector failed, run again to resume.
Change-Id: I91036c8e22b4c8c037d0e0fb702c709762b28777
Reviewed-on: https://chromium-review.googlesource.com/1304233
Commit-Ready: Kuang-che Wu <kcwu@chromium.org>
Tested-by: Kuang-che Wu <kcwu@chromium.org>
Reviewed-by: Chung-yih Wang <cywang@chromium.org>
1 file changed
