13.11 KB, text/csv
now that bm19 and bm20 are up and functional, let's get the tegras off of the old master
bm19/20 have lots of errors in the logs like Exception in /builds/buildbot/tests1-tegra/master/twistd.log: 2011-12-28 04:00:15-0800 [Broker,17895,10.250.48.224] Unhandled Error Traceback (most recent call last): Failure: twisted.cred.error.UnauthorizedLogin:
new tegras were added to the end of the defined range and those had buildbot running. i've turned off tegra-286 until the reconfig happens
from irc: (In reply to Mike Taylor [:bear] from comment #2) > new tegras were added to the end of the defined range and those had buildbot > running. once test-master01 is disabled in slave alloc, each tegra as it reboots will migrate from test-master03 to buildbot-master19/20 automatically. hwine will do this today. > i've turned off tegra-286 until the reconfig happens This issue is being tracked in bug#713161. tegra-286 is off and is not blocking moving all other tegras off test-master03.
Created attachment 585157 [details] Current foopy <-> tegra <-> buildbot master assignments CSV format with header
All production tegras moved from test-master01. Listing of current tegra -> build master assignments attached as a csv file. Current count of tegras: assigned to production: 213 assigned to staging: 36 total deployed: 249 NOTE: tegra dashboard will report incorrect status until bug 714462 is resolved.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.