New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 671481 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
█ robert...@chromium.org
hablich@chromium.org
dtu@chromium.org
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 671177



Sign in to add a comment

Bisect - Aborts with no message when both good/bad fail to reject.

Project Member Reported by simonhatch@chromium.org, Dec 6 2016 
https://bugs.chromium.org/p/chromium/issues/detail?id=671177#c5


Here was the output from that bug when it failed on chromium@435883 to reject either good or bad:

The bisect was aborted because Bisect cannot identify a culprit: 
Please contact the the team (see below) if you believe this is in error.



We should add a message here, maybe something more like:

The bisect was aborted because Bisect cannot identify a culprit: Could not continue after testing chromium@X against chromium@y (LKGR) and chromium@Z (FKBR) as comparing found no significant differences against either.
Please contact the the team (see below) if you believe this is in error.

Comment 1 by hablich@chromium.org, Dec 7 2016

Cc: hablich@chromium.org
In order to add my two cents:

I am missing the most important information for me: What should I do next? e.g.:

The bisect was aborted because no clear culprit could be identified. Next steps:

- Try a non-archive bisection (deeplink to create such a bisection)
- Increase repeat rate (deeplink to create such a bisection ... no clue if we even have that feature)
- Manually bisect on your computer (link to how to)

Comment 2 by simonhatch@chromium.org, Dec 8 2016 

I think this is a great idea, we just had another failure where removing --story-filter helped a lot. I think a list of things to try next would go a long way.

Comment 3 by benhenry@chromium.org, Feb 3 2017

Components: Speed>Bisection
►

Sign in to add a comment