Build:Mac:Moz2:ITSupport: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
Line 1: Line 1:
= Steps to Try =
= Steps to Try =
== Rebooting a slave ==
Logon to the machine, reboot it. Buildbot will come back up on boot.


== Intermittent Burning (not related to checkins) ==
== Clobbering a slave ==
This is often caused by a single slave having a problem such as a host key not accepted, out of disk space, etc.
Find the slave/builder combination on https://build.mozilla.org/clobberer/index.php and use the form to trigger a clobber. The next time that slave does the selected build, it will clobber first.
* If the problem is obvious (eg, hanging on a host key):
*# Log into the failing slave as 'cltbld'
*# Accept the host key/free some space(1)/whatever.
* If you don't know what the problem is:
*# Login to the slave as 'cltbld'
*# Stop the slave with 'buildbot stop /builds/moz2_slave'
*# Notify someone in RelEng to investigate further.
*# Note: Unless 3 or more slaves from a platform are failing the tree does not need to be closed.
 
(1) Slaves sometimes run out of disk space because of failed nightly builds that did not clean-up after themselves. Here's a helper script to clean those up:
for i in `find /builds/moz2_slave -maxdepth 1 -iname "*-nightly" -type d`; do find $i -maxdepth 1 -type d -iname build -exec rm -rf {} \;; done
== Fixing Failing Builds (clobber steps) ==
'''Login as cltbld with VNC (only use SSH if you do not need to start/stop any processes)'''
 
Clobber the failing slave and force a new build. (Note: forcing a new build will not necessarily cause a build on the failing slave. This is OK.)
# Find the hostname in the Tinderbox log (look for 'Building on: XXX' where 'XXX' is a hostname)
# Login to the slave using provided credentials (VNC for Mac).
## Go to the builder directory /builds/moz2_slave/$builder_name [where $builder_name matches the name of the failing build on Tinderbox]
## Delete the subdirectory named 'build'.
## Force a new build
### Click on the appropriate column title on the Waterfall (eg. 'OS X 10.5.2 mozilla-central build')
### Fill out the Force Build form. 'Branch to build' MUST be specified (branch name is part of the builders name. eg, mozilla-central or actionmonkey).
### Click 'Force Build'.
## If the next build doesn't go green, contact RelEng.
 
== Builds not happening at all ==
'''Make sure all slaves are connected'''
Note: do NOT use the 'Ping Builder' button on the Waterfall, it will break future builds
# Go to the Buildslave List page.
# For any slaves that are listed as 'NOT connected' we need to connect the slave:
## Login to the slave using provided credentials (VNC for Mac).
### Start Terminal if not already running.
### Start Buildbot with 'buildbot start /builds/moz2_slave'
### Minimize the Terminal window (do NOT close it).
 
Wait 30 seconds and check the Buildslave List page again.
If slaves still aren't connected contact RelEng.
 
 
'''It is almost always a bad idea to reboot the buildmaster VM. It runs multiple Buildbot masters. Unless it is completely unreachable please do not restart this machine without talking to someone from RelEng first.'''

Latest revision as of 17:08, 2 March 2009

Steps to Try

Rebooting a slave

Logon to the machine, reboot it. Buildbot will come back up on boot.

Clobbering a slave

Find the slave/builder combination on https://build.mozilla.org/clobberer/index.php and use the form to trigger a clobber. The next time that slave does the selected build, it will clobber first.

Retrieved from "https://wiki.mozilla.org/index.php?title=Build:Mac:Moz2:ITSupport&oldid=131309"