419799 - "WINNT 5.2 qm-win2k3-01 dep unit test" seems to have an open file

Status: VERIFIED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

"WINNT 5.2 qm-win2k3-01 dep unit test" on the Firefox tinderbox seems to have an open file.  This is holding the tree closed:

rm -f -rf ./dist/include
rm -f -rf ./dist/private
rm -f -rf ./dist/public
rm -f -rf _tests
make[1]: Leaving directory `/c/slave/trunk_2k3/mozilla/objdir'
rm: cannot remove directory `_tests/xpcshell-simple/xpcom/unit': Directory not empty
rm: cannot remove directory `_tests/xpcshell-simple/xpcom': Directory not empty
rm: cannot remove directory `_tests/xpcshell-simple': Directory not empty
rm: cannot remove directory `_tests': Directory not empty
make[1]: *** [default] Error 1
make: *** [build] Error 2

It sounds like there's something holding the file open.  Finding the simplest way to clear this up quickly would be helpful (e.g., terminating the open program holding it open if possible, otherwise rebooting without clobbering the tree so it doesn't cause an hourlong rebuild).


We need to get this fixed so we can land the necessary patches for beta4 and get it all in by around 3am.

First warning:
You must have rdesktop set to 24-bit color when connecting to this machine.  If you don't, it'll break the tests.  There's documentation on that on the page on tinderbox maintainance.

Second warning:
When you finish doing what you're doing, you need to make sure the appropriate window is focused or not.  I think there's documentation on that as well.  People on #developers will probably know.

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Avoiding a reboot may be preferable to prevent the color depth problem, although that may be a risk even without one -- not sure.

Avoiding deleting the tree would help get things started much faster.

Anyway, there's lots of people in #developers, and we can probably figure out in a few minutes whether a fix worked.

Comment 2

[matthew zeier [:mrz]]

Something had crashed when I RDP'd in but window closed before I could see what had crashed.  Restarted buildbot, nothing happened.  Killed buildbot and the cmd.exe it was running in and restarted buildbot in a new cmd.exe.

waterfall page shows progress.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

Thanks mrz!