Several CQ/paladin builders offline |
|||||||||||
Issue descriptionsince friday night the commit queue is not allowing any changes to go through. https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/10615 the failure seems to be very similar all the time: Ex: CommitQueueCompletion guado_moblab-paladin did not start. auron-paladin did not start. daisy-paladin did not start.
,
Mar 27 2016
,
Mar 27 2016
Many builders seem down on the CrOS waterfall. For example daisy-paladin has been not completing regularly and it looks like it's using it's backup builder: https://uberchromegw.corp.google.com/i/chromeos/builders/daisy-paladin The backup builder looks to be overwhelmed as it's building for many build types which it shouldn't really be. See https://uberchromegw.corp.google.com/i/chromeos/buildslaves/build111-m2 . Not sure what's going on here.
,
Mar 27 2016
Looking at the build111-m2 it looks to be a backup builder. So it seems like at least 5 of the CQ builders are offline (based on unique configs running on build111-m2). I see: build139-m2 build116-m2 build146-m2 build329-m2 build109-m2 all offline
,
Mar 28 2016
,
Mar 28 2016
build{139,116,146,109}-m2 are back up. Somebody connected up build329-m2
build189-m2 will be up in a bit (Noticed it was down too.)
,
Mar 28 2016
Re: build329-m2, that was me, i just started the buildbot process.
,
Mar 28 2016
Issue 598323 has been merged into this issue.
,
Mar 28 2016
,
Mar 28 2016
build189-m2 is now back up. I think this bug is now fixed?
,
Mar 28 2016
I think so. Thanks!
,
Apr 11 2016
,
Apr 27 2016
,
Apr 27 2016
,
May 23 2016
Bulk verified |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by llozano@chromium.org
, Mar 27 2016