769139 - Please manually clobber ionmonkey.*spidermonkey.* on mw32-ix-slave13

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

Description

[Phil Ringnalda (:philor)]

As https://tbpl.mozilla.org/php/getParsedLog.php?id=13052836&tree=Ionmonkey (and several more) say, "Couldn't clobber properly, bailing out." It's probably ionmonkey-w32-dbg-spidermonkey-nomethodjit that's got something unremovable, but we've been on a clobber spree and every job thinks it needs to be clobbered, and there's no really clear output in the log about which directory choked the clobberer, so please just clear out anything on that slave to do with ionmonkey and spidermonkey. Thanks!

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

I deleted three ionmonkey-* dirs and rebooted.

There was a ionmonkey_win32-debug_spidermonkey-nomethodjit on 7fa6fdc6d1cf at Wed Jun 27 11:29:49 2012, which appears to have hung and then not been cleaned up properly:
TEST-PASS | jit_test.py --no-ion -d    | e:\builds\moz2_slave\ionmonkey-w32-dbg-spidermonkey-nomethodjit\src\js\src\jit-test\tests\ion\range-test-and.js

command timed out: 3600 seconds without output, attempting to kill
SIGKILL failed to kill process
using fake rc=-1
program finished with exit code -1

remoteFailed: [Failure instance: Traceback from remote host -- Traceback (most recent call last):
Failure: exceptions.RuntimeError: SIGKILL failed to kill process

Comment 2

[Phil Ringnalda (:philor)]

Ah, thanks - filed bug 769142 on rebooting, since SM is a lot of the use of win32 slaves now that only beta and below use them for builds.