The first set of checkins after 402853 that caused a rebuild of layout/ made Windows tinderboxen (nightly and unit test) to go red. Reed was able to clobber the nightly box but not the unit test boxes. <reed> file a blocker IT bug <reed> to remove the objdir

What box is this? hostname please.

Both qm-winxp01 and qm-win2k3-01. Try solution #3 first and then do solution #1.

aravind's having connectivity issues right now, so taking this

qm-winxp01 has been kicked. working on qm-win2k3-01, but it's being a pain in the ass.

ok, qm-win2k3-01 has been kicked.

Ever since these boxes were kicked 24 of the mochitests are failing. The previous green result on am-winxp01 was a clobber build, and the first orange failure is also a clobber. all checkins between the 2 builds have been backed out. I suspect it has something to do with the way these 2 servers were restarted. One thing I seem to recall caused issues in the past was connecting to the server via RDP to start the tinderbox script. Seems to me I recall it has to be done via VNC (or something like that).

(In reply to comment #6) > One thing I seem to recall caused issues in the past was connecting to the > server via RDP to start the tinderbox script. Seems to me I recall it has to > be done via VNC (or something like that). That doesn't apply to these boxes. That's true for some of the performance testing machines. I'll try a full clobber on the source directory.

(In reply to comment #7) > I'll try a full clobber on the source directory. > I have no idea why that should be necessary, but if I do a full source clobber on my winxp system and do a build all the mochitests pass, so it is definitely worth a shot.

robcee's full source clobber did fix the orange (I don't know why). Bug 403398 has been filed on making it possible for developers to force such a clobber on the unit test boxes; apparently it's already possible on the nightly boxes.