New issue
Advanced search Search tips

Issue 765145 link

Starred by 2 users
Status: Fixed
Owner: ----
Closed: Sep 2017
Cc:
josephsih@chromium.org
seobrien@chromium.org
yueherngl@chromium.org
osh...@chromium.org
no...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

CommitQueueCompletion: The master destructed itself and stopped waiting for the following slaves

Project Member Reported by josephsih@chromium.org, Sep 14 2017 
[ADD relevant info inline]

CommitQueueCompletion: The master destructed itself and stopped waiting for the following slaves

wolf-paladin: cbuildbot failed
... more ...
about 30 or 40 paladin cbuildbot failed

There were a series of 7 such continuous CommitQueueCompletion errors.


Link to build or pfq page.

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


build # for that buildbot.

16253 - 16259


Snippet of log that contains the failure.

https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16259/steps/CommitQueueCompletion/logs/stdio  showed

03:14:15: INFO: Got timeout for build_id 1848602

03:14:56: INFO: Uncompleted build poppy-paladin haven't passed stage UploadPrebuilts. The master can't publish uprevs now.

03:23:05: WARNING: This build will self-destruct given the results of relevant change triages.

@@@STEP_LINK@wolf-paladin: cbuildbot failed@https://luci-milo.appspot.com/buildbot/chromeos/wolf-paladin/15643@@@

...more paladin cbuildbot failed...

Comment 1 by josephsih@chromium.org, Sep 14 2017

Cc: seobrien@chromium.org yueherngl@chromium.org osh...@chromium.org josephsih@chromium.org
https://uberchromegw.corp.google.com/i/chromeos/builders/kevin-paladin/builds/2404/steps/BuildPackages/logs/stdio

Failed chromeos-base/android-container-nyc-4334671-r1 (in 0m1.3s). Your build has failed.

Might be problem of this CL: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/641923

I have marked verified-1 to the above CL. If CQ passed, we could close this issue.

Comment 2 by seobrien@chromium.org, Sep 14 2017

Status: Fixed (was: Untriaged)
This was caused by:

https://chromium-review.googlesource.com/c/chromiumos/chromite/+/664264

and the revert has fixed it.
►

Sign in to add a comment