Closed
Bug 1015116
Opened 12 years ago
Closed 11 years ago
runslave.py fails to use existing buildbot.tac after getting a 404 from slavealloc
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nthomas, Unassigned)
Details
During the great Apache blowup of 22 May, slavealloc must've been out of action for a while. A lot of mac and windows test slaves that rebooted about then ended up just sitting with no buildbot running (slave rebooter not recovering them will be filed separately). Here's some output from a /c/builds/runslave.log on a windows box:
"starting runslave.py Thu 05/22/2014 14:14:32.56"
WARNING: error fetching and/or replacing buildbot.tac file http://slavealloc.build.mozilla.org/gettac/T-W732-IX-033
Full exception: HTTP Error 404: Not Found
WARNING: falling back to existing buildbot.tac
Error sending notice to nagios (ignored)
FATAL: no buildbot.tac found; cannot start
Comment 1•11 years ago
|
||
WONTFIX in favor of bug 1135818.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•