Please help restart chromium.fyi |
||||
Issue descriptionI just added a new builder to chromium.fyi: https://chromium-review.googlesource.com/c/chromium/src/+/1073071 and https://chrome-internal-review.googlesource.com/c/infradata/config/+/630236. Do I need to restart the master in order to let the changes take effect?
,
May 29 2018
This is a LUCI builder, which means there is no master to restart. The builder exists, but has no bots assigned to it - something is probably misconfigured. Let me take a closer look...
,
May 29 2018
Thanks for the pointers Sergey. The above mentioned two CLs are the only two I landed to configure this builder, not sure if I missed anything.
,
May 29 2018
The corresponding pending task: https://chromium-swarm.appspot.com/task?id=3dc6334a78bd8710 reports that it has 0 bots to run on, while the assigned bot https://chromium-swarm.appspot.com/bot?id=swarm2226-c4 seems to exist and sitting idle. The reason, it seems, the bot currently belongs to pool:unassigned, while the builder expects it to be in pool:luci.chromium.ci. Apparently, it was removed in https://crrev.com/i/631187 (bad rebase?). So you just need to re-land your bots.cfg change, and it should work. Assigning back to you.
,
May 29 2018
+hinoka@ FYI - in case the above CL was generated by a script (it deleted a recently added bot).
,
May 29 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by liaoyuke@chromium.org
, May 29 2018