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

Issue 614975 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
█ robert...@chromium.org
█ pras...@chromium.org
dtu@chromium.org
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 603937


Sign in to add a comment

I can't understand bisect output

Project Member Reported by falken@chromium.org, May 26 2016 
https://chromeperf.appspot.com/group_report?bug_id=614367

Not sure if I should use the "bad_bisect" link, but I have some questions:
- Status is "started". Does that mean it's not finished?
- In case it's finished, is the result the range 395211-395217?
- What is Score: 0?
- If it's finished, shouldn't it have posted on the linked bug?

Comment 1 by falken@chromium.org, May 26 2016 

Now I clicked through the Job details link:
https://chromeperf.appspot.com/buildbucket_job_status/9011776611467111904

There is more info there:
    "result": "FAILURE", 
    "status": "COMPLETED", 

Maybe failed bisects should post on the bug anyway, so we know not to wait any longer for them.

Comment 2 by sullivan@chromium.org, May 26 2016

Blockedon: 603937
Cc: robert...@chromium.org dtu@chromium.org pras...@chromium.org
cc-ing bisect team. Agreed we could have clearer output, this is on our Q2 OKRs.

We've been discussing the best way to handle failures. Currently it retries instead of posting the failure on the bug. It sounds like that's not what your expectation as a user is?

Comment 3 by falken@chromium.org, May 26 2016 

Thanks! Retrying sounds fine, but the status shown at https://chromeperf.appspot.com/group_report?bug_id=614367 didn't make clear it was retrying.

I'm not sure it actually was retrying? I manually started two new jobs on 2016-05-26 (upon filing this bug) that have completed. The 2016-05-24 job still says Status: started.
Screen Shot 2016-05-26 at 10.01.02 PM.png
48.2 KB View Download

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

Components: Speed>Bisection

Comment 5 by simonhatch@chromium.org, Feb 7 2017

Status: WontFix (was: Untriaged)
Closing out old bugs, output has been completely refactored since this was filed.
►

Sign in to add a comment