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 with VNC
in the Terminal window, type "buildbot stop slave"
- note: message about not returning is expected on Mac
if necessary, reboot machine (if it appears to be responding strangely. I think we've only rebooted it once or twice since incept)
in a Terminal window,
- cd /builds/
- 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 with VNC
stop the slave (as above, buildbot stop slave)
- cd /builds/slave/
- rm -rf trunk_osx
restart the slave
- cd /builds
- buildbot start slave
  - message that buildbot didn't return is expected

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:Linux: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-centos5-02, qm-centos5-04, qm-xserve01, qm-xserve06, qm-win2k3-01, qm-win2k3-02, qm-win2k3-pgo01
verify waterfall at http://qm-rhel02.mozilla.org:2005/ is visible and slaves are connected