The fix has already landed (attachment 608801 [details] [diff] [review] from bug 737458) and is just awaiting a reconfig, but apparently having 18 unstarred red jobs is not enough to stop us from pushing, and because I know us too well, pointing the tree closure notice at a resolved bug would just wind up with someone reopening. mozilla-beta's closed, and will stay closed until we've got working talos retriggered on the two code pushes that didn't get it (87a101ff217b and the mozconfig cleanup from last week can do without).

jhford is planning to reconfig Tuesday morning for b2g builds, for which his changes are already landed. I could transplant just the talos fix but the go for 12.0b3 looks like it will come late Tuesday, and I'd hope that anyone with approval already landed on beta, so I don't think waiting will hold that up.

They haven't - roc just landed something on aurora that also has approval-beta.

Yeah :-)

Unhorking buildbot-configs: http://hg.mozilla.org/build/buildbot-configs/pushloghtml?fromchange=22366773e346&tochange=1dc551485720

One more since I undid a bit too much: http://hg.mozilla.org/build/buildbot-configs/rev/5a867d627c82 Test masters updated: bbc bb-c tools buildbot Before 3995dac97820 36ce86337cb2 24cf416d1953 a2045101fe7a After 3995dac97820 5a867d627c82 96524f81c613 a2045101fe7a and reconfig'd. Unfortunately bm20-tests1-tegra got a hard restart after it failed to reconfig, and it got into a bad state when I tried to repeat that.

Same for the two schedulers on bm10.

Sendchanges have been redone on 0b4ec3bcf064 & a8b5d0ac89ff, which will get new sets of talos for each platform.

Builds are green, tree is open.