148
edits
ReleaseEngineering/How To/Handle an Idle Slave: Difference between revisions
ReleaseEngineering/How To/Handle an Idle Slave (view source)
Revision as of 09:08, 24 November 2017
, 24 November 2017Updated the instructions on how to deal with an idle slave(2)
(Updated the instructions on how to deal with an idle slave) |
(Updated the instructions on how to deal with an idle slave(2)) |
||
| Line 3: | Line 3: | ||
** https://secure.pub.build.mozilla.org/builddata/reports/slave_health/index.html | ** https://secure.pub.build.mozilla.org/builddata/reports/slave_health/index.html | ||
** any machine that hasn't taken a job for a time period > 5 hours is considered "idle" and the row color for the corresponding machine will turn orange. | ** any machine that hasn't taken a job for a time period > 5 hours is considered "idle" and the row color for the corresponding machine will turn orange. | ||
** also look at the number of recent running/pending jobs for that pool of machines. Sometimes, it is only normal for those machines to be idle since the load is lower. | |||
* check buildbot.tac to ensure the slave is enabled and see which master it's on. | * check buildbot.tac to ensure the slave is enabled and see which master it's on. | ||
* tail twistd.log to see if the slave is really idle. In most cases, the slave has been idle since it started up. Note any differences. | * tail twistd.log to see if the slave is really idle. In most cases, the slave has been idle since it started up. Note any differences. | ||
* Reboot. Don't use `buildbot restart`, since it won't work on macs! | * Reboot. Don't use `buildbot restart`, since it won't work on macs! | ||