ReleaseEngineering/How To/Handle an Idle Slave

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
  • check SlaveHealth dashboard for idle machines
    • 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.
    • 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.
  • 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!
Retrieved from "https://wiki.mozilla.org/index.php?title=ReleaseEngineering/How_To/Handle_an_Idle_Slave&oldid=1184711"