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

Issue 790017 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: ----



Sign in to add a comment

master CQ has self-destructed slaves but still pass

Project Member Reported by xixuan@chromium.org, Nov 30 2017

Issue description

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

We have several purple slaves, but master still pass. Why are these slaves purple?

 

Comment 1 by xixuan@chromium.org, Nov 30 2017

Cc: slavamn@chromium.org drinkcat@chromium.org athilenius@chromium.org

Comment 2 by nxia@chromium.org, Nov 30 2017

Status: WontFix (was: Untriaged)
this is expected


https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fmaster-paladin%2F17074%2F%2B%2Frecipes%2Fsteps%2FCommitQueueCompletion%2F0%2Fstdout



09:15:43: INFO: will_submit set contains 9 changes: [CL:*518333 CL:*518375 CL:779403 CL:796850 CL:797614 CL:798793 CL:798794 CL:798934 CL:798952]
might_submit set contains 0 changes: []
will_not_submit set contains 0 changes: []
09:15:43: WARNING: This build will self-destruct given the results of relevant change triages.
09:15:43: INFO: This build will self-destruct with success.

Comment 3 by nxia@chromium.org, Nov 30 2017

The master found it was going to submit all CLs given the passed slaves, so it decided to self-destruct and kill the remaining running slaves.

Sign in to add a comment