New issue
Advanced search Search tips

Issue 847603 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Please help restart chromium.fyi

Project Member Reported by liaoyuke@chromium.org, May 29 2018

Issue description

I 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?
 
Here is the link to the console view:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-code-coverage-generation

No bots seem to be connected.
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...
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.
Owner: liaoyuke@chromium.org
Status: Assigned (was: Untriaged)
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.
Cc: hinoka@chromium.org
+hinoka@ FYI - in case the above CL was generated by a script (it deleted a recently added bot).
Status: WontFix (was: Assigned)

Sign in to add a comment