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

Issue 803895 link

Starred by 1 user
Status: Fixed
Owner:
█ nxia@chromium.org
Last visit > 30 days ago
Closed: Jan 2018
Cc:
lannm@google.com
akes...@chromium.org
█ shuqianz@chromium.org
dgarr...@chromium.org
sonnyrao@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

moblab-generic-vm-paladin failed but CQ passed

Project Member Reported by shuqianz@chromium.org, Jan 19 2018 
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/17524

moblab-generic-vm-paladin failed at HWTest stage due to the following erorr:The MoblabVMTest stage failed: Moblab run_suite succeeded, but did not successfully run dummy_PassServer

Then CQ chose to destructed itself and stopped waiting for the following slaves:

caroline-paladin: aborted by self-destruction
veyron_minnie-paladin: aborted by self-destruction
cyan-paladin: aborted by self-destruction
cave-paladin: aborted by self-destruction
auron_yuna-paladin: aborted by self-destruction 

At the end, the CQ marked itself as passed. Is this expected? How could a slave fail but master pass?

Comment 1 by lannmar...@gmail.com, Jan 19 2018 

It looks like all of the CLs had passed all the tests they needed so the build short circuited itself to save time.

Comment 2 by shuqianz@chromium.org, Jan 19 2018 

nxia@, do we have that kind of smart CQ mechanism as #2 mentioned?

Comment 3 by nxia@chromium.org, Jan 19 2018 

Yes, all the relevant slaves of the CLs to test passed, so the CQ destructed itself with success.

09:12:44: INFO: Moving CL:*546618 CL:*549938 CL:*549978 CL:872457 CL:874760 CL:874761 to will_submit set, because their relevant builds completed successfully or all failures are ignorable or passed in CQ history.
09:12:44: INFO: will_submit set contains 6 changes: [CL:*546618 CL:*549938 CL:*549978 CL:872457 CL:874760 CL:874761]
might_submit set contains 0 changes: []
will_not_submit set contains 0 changes: []
09:12:44: WARNING: This build will self-destruct given the results of relevant change triages.
09:12:44: INFO: This build will self-destruct with success.

Comment 4 by shuqianz@chromium.org, Jan 19 2018

Status: Fixed (was: Assigned)
Good to know
►

Sign in to add a comment