It’s CLOBBERin’ time!
That’s right, gentle reader, the unit test boxes (qm-rhel02, qm-winxp01 and qm-xserve01) are now supporting Tinderbox’ clobber support. Updating the contents of (or just touching) mozilla/tools/tinderbox-configs/firefox/$platform/CLOBBER (where $platform is in [macosx, linux, win32]) will cause mozilla/objdir to be deleted. Ideally, you should include a short note in the CLOBBER file about why you’re clobbering. This will show up in the unit test boxes’ logs. Also, your checkin comment to CVS should clearly-state that you’re doing a clobber (and ideally your bug number). As it states in the instructions, try to coordinate in irc:#developers so as not to stack multiple clobbers.
But wait, there’s more! The Windows unit test box, qm-winxp01 gets special treatment. A clobber request will cause that machine to kill a running firefox process. So if, say, a mochitest was frozen from a previous run, clobbering the box should kill that process and hopefully builds and unit tests can proceed as usual.
Sorry for the burning boxes these past couple of days. In the future I’ll go back to my previous development plan of working locally and rolling changes out to the farm when fully-tested on my dev boxes. Who knew killing a process on Windows (or, heck, just deleting a directory with Python) could be such a pain?

3 Comments