qm-win2k3-01 continues to have problems. Please restart the machine, remove the objdir, and start buildbot. Thanks!
If this continues to have problems like this (and has had similar issues in the past), is it probably something build should look at fixing?
(In reply to comment #1) > If this continues to have problems like this (and has had similar issues in the > past), is it probably something build should look at fixing? QA manages this box, not Build, but yes, I agree. However, we need more immediate action on this box, as it is stopping us from having unit tests running on Windows 2003, so that's why we need IT intervention.
killed the running buildbot slave process removed objdir rebooted the box started slave and followed instructions to force build. Dropping severity on the bug and sending it on to robcee who seems to know the most about this stuff.
this has been happening consistently since sspitzer's checkin on 11/5 @ 21:31 (bug 399664). The failures all appear to be xul failures and since seth's patch was backed out again and they're still failing, I'm wondering if there's something in the source tree on that machine that didn't get cleared out by the clobber. I'll try removing the source-tree and starting another build to see if this clears it up. If it doesn't, I'm inclined to think there's a real problem here.
This seems to have cleared up the problem.