Notes and Caveats

Steps to Try

Please try these steps in order - if the third step (manual clobber) doesn't work contact bhearsum or robcee.

check waterfall at: http://qm-rhel02.mozilla.org:2005/ (mpt-vpn)
see if slave is connected.
if so, click the machine name link, try a "Force Build"
- fill out the name and reason fields, click the button

login to machine using provided credentials
in the Terminal, type "buildbot stop slave" (pwd should be /builds/)
reboot if necessary (never needed to yet)
restart buildbot:
- cd /builds/ (should already be there)
- buildbot start slave
check the waterfall at: http://qm-rhel02.mozilla.org:2005/
the slave sometimes takes a couple of minutes to reconnect
if it does, and is necessary, click the machine name link and force a build as above (fill name and reason fields, click the button)

Sometimes a machine will need to be "clobbered" (have its build directory removed inside the slave dir)
login to the machine
stop the slave (as above, buildbot stop slave)
- cd /builds/slave/trunk_centos5_2/mozilla
- rm -rf objdir
restart the slave
- cd /builds
- verify Xvfb is running in the other Xterm
  - if not, enter "Xvfb -screen 0 1280x1024x24 :2 &" in the second Xterm
- ignore any metacity already running on display1.
- if no metacity is running on display2, run:
  - DISPLAY=:2 metacity &
- cd /builds
- DISPLAY=:2 buildbot start slave

Contact Robcee or Bhearsum if you need to go to Step 4

In the worst case, the entire buildbot farm needs to be restarted
shutdown each slave as per the instructions: Unittest:WinXP:ITSupport Unittest:Mac:ITSupport
shutdown master on qm-rhel02
- cd /build
- buildbot stop master
reboot qm-rhel02 and slave machines if necessary (stuck processes, strange behavior)
restart master on qm-rhel02
- cd /build
- buildbot start master
restart slaves as above
- qm-centos5-01, qm-xserve01, qm-winxp01, qm-win2k3-01
verify waterfall at http://qm-rhel02.mozilla.org:2005/ is visible and slaves are connected