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

Issue 664503 link

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

Blocking:
issue 664494
issue 664479



Sign in to add a comment

Confusing bisect bug comments on failure

Project Member Reported by sullivan@chromium.org, Nov 11 2016 
Example:
https://bugs.chromium.org/p/chromium/issues/detail?id=664136#c7

There is no Mean and Std Dev, but dashboard still prints both. It's confusing to print all the output when the job failed.

Comment 1 by robert...@chromium.org, Nov 11 2016 

This might be related to the lack of a result code. The fix for compare samples should address this.

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

The job in c#2 is failing due to  Bug 664724  that has been fixed. Another attempt is scheduled: https://chromeperf.appspot.com/buildbucket_job_status/8996212001977832144

Comment 4 by sullivan@chromium.org, Nov 12 2016

Blocking: 664479

Comment 6 by robert...@chromium.org, Nov 14 2016

Status: Fixed (was: Untriaged)
Correct output: https://bugs.chromium.org/p/chromium/issues/detail?id=664479#c8

Note that failure to find a culprit is still a failed bisect as per the new statuses in the refactor.

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

Components: Speed>Bisection
►

Sign in to add a comment