726742 - pull talos-r3-w7-065 out of the pool

Status: RESOLVED DUPLICATE of bug 727551

(Release Engineering :: General, defect)

Description

[Armen [:armenzg]]

armenzg_buildduty: could you please rm build/xpcshell/tests/xpcom/tests/unit on talos-r3-w7-065 so we don't have to wait until the next time it runs xpcshell to have it stop turning everything it does red?

Pulled in slavealloc.

Comment 1

[Phil Ringnalda (:philor)]

The longer explanation, for anyone who hasn't met it yet, is that bug 582821 leaves the file locked when it hits, and then rm -rf build fails ("rm: cannot remove directory `build/xpcshell/tests/xpcom/tests/unit': Directory not empty") on every sort of run that slave does which does rm -rf build, until the next time that slave does xpcshell again, when the test apparently manages to unlock it again and successfully run.

Comment 2

[Armen [:armenzg]]

Nice :)

It seems that "rmdir /s /q" fixes it.

Both talos-r3-w7-065 and talos-r3-w7-066 are back to the pool.

We will keep this bug open to figure out what the correct way of solving this is.
I think bug 727551 would take too long to there.

I will try something on staging.

##################################
C:\talos-slave\test>rm -rf build
rm: reading directory `build/xpcshell/tests/xpcom/tests/unit': Invalid argument
rm: cannot remove directory `build/xpcshell/tests/xpcom/tests': Directory not em
pty

C:\talos-slave\test>rmdir /s /q build

C:\talos-slave\test>rm -rf build

Comment 3

[Armen [:armenzg]]

No point on having multiple bugs open.