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

Issue 660439 link

Starred by 1 user
Status: Duplicate
Merged: issue 661777
Owner:
█ robert...@chromium.org
Last visit > 30 days ago
Closed: Nov 2016
Cc:
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Untestable reference range should fail bisect

Project Member Reported by robert...@chromium.org, Oct 28 2016 
If either revision in the reference range has no values, bisect should raise an issue.

Comment 1 by robert...@chromium.org, Oct 28 2016 

E.g. https://build.chromium.org/p/tryserver.chromium.perf/builders/staging_linux_perf_bisect/builds/17

This bisect seems successful until you see the data: neither revision has a single value to compare. Bisect seems to find a culprit base on the assumption that the "good" revision is "good" and the "bad" revision is "bad"

Comment 2 by robert...@chromium.org, Nov 3 2016

Mergedinto: 661777
Status: Duplicate (was: Assigned)

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

Components: Speed>Bisection
►

Sign in to add a comment