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

Issue 738033 link

Starred by 1 user
Status: Duplicate
Merged: issue 738139
Owner: ----
Closed: Jun 2017
Cc:
█ jrbarnette@chromium.org
█ cernekee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

pyro-release seems flaky

Project Member Reported by sjg@google.com, Jun 29 2017 
Various failures over the past week

https://luci-milo.appspot.com/buildbot/chromeos/pyro-release/


pyro-release:776 failed

Builders failed on: 
- pyro-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/pyro-release/776

Comment 1 by jrbarnette@chromium.org, Jun 30 2017 

There's no single cause of failure for pyro.  Overall,
evidence is that the canary is reasonably healthy.  The
last two builds seem to have failed primarily because of
swarming errors.  So, this could be related to  bug 738139 .

Comment 2 by jrbarnette@chromium.org, Jun 30 2017

Mergedinto: 738139
Status: Duplicate (was: Available)
> There's no single cause of failure for pyro.

I take it back, the last several failures all stem from
swarming failures.

Let's call this a duplicate.
►

Sign in to add a comment