Oopsie. Last time we were desperate to get some headroom under MAX_BROKER_REFS, we commented Pine out of configs, which was fine except for the way we apparently didn't think to mark it as booked, so now anant is wonder why, after he followed all the instructions to book the twig and get the repo reset, he isn't getting any builds or tests run. My (outside watcher, not employee, not insider) feeling is that we're still desperately short, and that if we had enough room which we don't Alder is first in line, because it has been wanting tests turned on and been unable to get them for a while now, so the only open course of action is to quickly grab another twig before the open ones get booked. You can see (once bitten, twice shy) from http://mxr.mozilla.org/build/source/buildbot-configs/mozilla/project_branches.py#261 that only Pine is commented out, but personally unless I was going to be doing mobile nightly update testing I'd take Larch rather than Maple, which still hasn't been uncustomized from when it was the Android native trunk.

Larch and Maple are both free, would it be possible to book one of those two on behalf of Build, disable it, and enable Pine instead? That would save us a tree migration, which I would really appreciate. Thanks for the info!

I've grabbed Larch on the booking page. Patch coming up.

Comment on attachment 623534 [details] [diff] [review] [buildbot-configs] Disable larch, enable pine http://hg.mozilla.org/build/buildbot-configs/rev/0d291d81c5e0 Anant, this will go live the next time the builduty person deploys changes to the buildbot masters.

Thanks guys, that's great!

A change from this bug landed on the default branches of either buildbot-configs or buildbotcustom. Such change has been merged as of ~8:30 AM PDT into the production branches and the buildbot masters have been reconfigured. This if FYI and a note has been added to the maintenance page: https://wiki.mozilla.org/ReleaseEngineering:Maintenance#Reconfigs_.2F_Deployments