The two Windows unit-test boxes on Firefox trunk need to be clobbered, but they don't seem to be checking for auto-CLOBBER support. Please remove the objdir from both of these machines.
I'm pretty sure these boxes support clobbering like the main tinderboxes do. That is, add a comment to mozilla/tools/tinderbox-configs/firefox/win32/CLOBBER (and also linux and macosx) and commit them. The test_unit branch is used for these boxes.
Ok, I hadn't known about the test_unit branch, so I've committed a CLOBBER revision there, and I'm hoping for the best.
That didn't work. Back to requesting a manual clobber.
I don't think we support these boxes. Sending this to build/release. Was asked to cc robcee on the bug
(In reply to comment #4) > Was asked to cc robcee on the bug FYI, AIUI, this was originally filed because robcee is on vacation.
Sorry to keep bouncing, we don't have access to these machines at all.
I am not sure we do either.. Dropping serverity, so it doesn't page us.
Adding my stamp of approval for the clober since robcee is out of town.
Okay, I wiped out the objdir in qm-winxp01 and restarted the command that was running earlier.
Did the same for qm-win2k3-01.
so, I'm just wondering, was it deemed too damaging to clobber all windows tinderboxes using the watched cvs files? Good work getting it resolved anyway. Thanks. :)
(In reply to comment #11) > so, I'm just wondering, was it deemed too damaging to clobber all windows > tinderboxes using the watched cvs files? See comment 1 through comment 3 - is that not the right way to attempt a manual clobber? I thought they just used HEAD and not "test_unit" myself, but then I also remember hearing that the clobber directives don't actually trigger new builds on their own and that you need to additionally check in files that are part of the "module" the CVS-poller watches (PhoenixTinderbox?), so I suppose any one of those things could have gone wrong here. Perhaps it would be a good idea to add unit-test-box specific information at http://wiki.mozilla.org/Build:ClobberingATinderbox ?
yeah, just checking HEAD now. We talked about adding a unit-test-specific clobber file so as not to hose the whole tree. After talking with Benjamin and looking into what happened a bit more, I determined that the Win2k3 wasn't clobbering properly because of some frozen shell and make processes which seem to hang around when the system exits uncleanly. https://bugzilla.mozilla.org/show_bug.cgi?id=381004