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

Issue 590863 link

Starred by 1 user
Status: WontFix
Owner:
█ sbasi@chromium.org
Last visit > 30 days ago
Closed: Apr 2017
Cc:
█ jrbarnette@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

PFQ failures with "stage_artifacts timed out"

Project Member Reported by steve...@chromium.org, Feb 29 2016 
Tracking bug for PFQ failure symptom "stage_artifacts timed out".

Searching the issue tracker shows many of these, all Untriaged or WontFix.

Not all failures generate an issue, e.g.
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_minnie-cheets%20paladin/builds/190

Comment 1 by jrbarnette@chromium.org, Feb 29 2016

Labels: Infra-ChromeOS
There's an ongoing problem with devserver load that could cause this
kind of symptom (among others).

Comment 2 by steve...@chromium.org, Mar 7 2016

Status: Assigned (was: Untriaged)
This is still occurring sporadically. We've had 8 failures in the past 12 hours.

Comment 3 by benhenry@google.com, Apr 26 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS

Comment 4 by michae...@chromium.org, Apr 27 2017

Status: WontFix (was: Assigned)
These failures seem to happen in batches and have been caused by infra outages/overloads or particular issues, like issue 659850.

So, I don't think this bug is useful as the items it would track should just be handled as they come up. Feel free to re-open if you disagree.
►

Sign in to add a comment