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

Issue 599982 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

daisy-paladin did not start

Project Member Reported by moch@chromium.org, Apr 1 2016

Issue description

https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/10665

Log file:
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/10665/steps/CommitQueueCompletion/logs/stdio

See the following repeated quite often:
ERROR: No status found for build config daisy-paladin

@@@STEP_TEXT@daisy-paladin did not start.@@@

@@@STEP_WARNINGS@@@
13:24:07: WARNING: The following builders did not start or failed prematurely:
daisy-paladin
Please check the logs of these builders for details.
13:24:08: INFO: Refreshing due to a 401 (attempt 1/2)
13:24:08: INFO: Refreshing access_token
13:24:08: INFO: Running cidb query on pid 24237, repr(query) starts with 'SELECT bs.id, bs.build_id, bs.name, bs.board, bs.status, bs.last_updated, bs.start_time, bs.finish_
13:24:08: WARNING: Config(s) daisy-paladin did not complete critical stage CommitQueueSync.
13:24:08: WARNING: Not doing any partial submission, due to critical stage failure(s).
13:24:12: WARNING: Detected that the build failed due to non-lab infrastructure issue(s). Will only reject chromite changes
 
Mergedinto: 600062
Status: Duplicate (was: Untriaged)

Sign in to add a comment