Issue metadata
Sign in to add a comment
|
master-paladin does not kick off build for slave paladins |
||||||||||||||||||||||||
Issue descriptionSorry if my terminology is incorrect, I'm referring to auron-paladin as a slave paladin. Since build #10600, the master paladin starts a build but seems to miss starting certain slave paladins (auron-paladin for #10600). I don't see a build from auron-paladin that has the master build-id recorded for #10600 (773899). Auron-paladin is building fine though. master-paladin build #10600 failed with: "CommitQueueCompletion auron-paladin did not start." auron_paladin has two builds that start before and after #10600 and both don't have a master build-id that correspond to 773899. master #10600 start: Fri Mar 25 19:50:15 2016 end: Fri Mar 25 21:16:22 2016 build id: 773899 https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/10600 auron-paladin #6621 start: Fri Mar 25 17:07:14 2016 end: Fri Mar 25 18:12:28 2016 master build id: 773750 https://uberchromegw.corp.google.com/i/chromeos/builders/auron-paladin/builds/6621 auron-paladin #6622 start: Fri Mar 25 22:53:42 2016 end: Fri Mar 25 23:58:24 2016 master build id: 774075 https://uberchromegw.corp.google.com/i/chromeos/builders/auron-paladin/builds/6622
,
Mar 28 2016
,
Mar 28 2016
AFAIK neither of these was kicked. build111-m2 is the floating builder. The previous bump/restart request was not completed and some slaves were offline, so it was filling in for them. Since it can only do one build at a time, this explains the behavior. I have kicked the offline slaves, so things should be stable now.
,
Apr 27 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by akes...@chromium.org
, Mar 28 2016