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

Issue 684121 link

Starred by 1 user
Status: Duplicate
Owner:
fmea...@chromium.org
Closed: Jan 2017
Cc:
█ mikec...@chromium.org
chrome-trooper-bugs@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocking:
issue 683999



Sign in to add a comment

purple winx64_bisect_builder: failing on first step

Project Member Reported by simonhatch@chromium.org, Jan 23 2017 
https://uberchromegw.corp.google.com/i/tryserver.chromium.perf/builders/winx64_bisect_builder/builds/5049

80:0Traceback (most recent call last):
Failure: buildslave.exceptions.AbandonChain
,


+fmeawad as bothealth sheriff

Comment 1 by fmea...@chromium.org, Jan 23 2017

Mergedinto: 683940
Status: Duplicate (was: Untriaged)
That issue has been fixed. Duplicating to the original report.

Re-open if it still exists.

Comment 3 by simonhatch@chromium.org, Jan 24 2017

Status: Assigned (was: Duplicate)

Comment 4 by fmea...@chromium.org, Jan 24 2017

Mergedinto: -683940 683889
Status: Duplicate (was: Assigned)
It seems that it needs to have rebooted at least once to pick up the fix.

Comment 5 by simonhatch@chromium.org, Jan 24 2017 

Sent jobs to every win bisect bot + each slave. Everything went purple but it looks like it's recovered.
►

Sign in to add a comment