690337 - w64-ix-slave36 may need to be reimaged

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Joey Armstrong [:joey]]

rm: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.

This may be the source of bug 684095.  Not an isolated incident the random packaging error has shown up on several different try submissions.
======================================================================

builder: try-win64
slave: w64-ix-slave36
starttime: 1317284393.55
results: failure (2)
buildid: 20110929012056
builduid: 64841f82d1d74a64bf0e0033bc832296
revision: 4822254e25e3

========= Started 'rm -rf ...' failed (results: 2, elapsed: 6 mins, 25 secs) ==========
'rm' '-rf' 'build'

rm: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
  `build/security/nss/lib'

program finished with exit code 1
======== Finished 'rm -rf ...' failed (results: 2, elapsed: 6 mins, 25 secs) ========


All kinds of fun after the fact:
abort: There is no Mercurial repository here (.hg not found)!
abort: There is no Mercurial repository here (.hg not found)!


tar: vmwarerecordinghelper.dll: Cannot stat: No such file or directory
grep: components/*.manifest: No such file or directory
sed: can't read components/*.manifest: No such file or directory
Can't find 'chrome.manifest' in ./omni.jar
Can't find 'components/interfaces.manifest' in ./omni.jar
Can't find 'components/browser.xpt' in ./omni.jar

Can't find 'jsloader/resource/gre/modules/DownloadTaskbarProgress.jsm' in ./omni.jar
sed: can't read components/*.manifest: No such file or directory
make[4]: *** [repackage-zip] Error 2
make[3]: *** [repackage-win32-installer] Error 2
make[2]: *** [repackage-win32-installer-x-test] Error 2
make[1]: *** [l10n-check] Error 2
make: *** [l10n-check] Error 2
program finished with exit code 2

Comment 1

[Joey Armstrong [:joey]]

bug # should be 650504 not bug 684095

Comment 2

[Armen [:armenzg]]

I was going to disable the slave and leave it for joey to do a manual clobber but it seems that the next job was able to clobber it.

Joey I have retriggered your job.

Comment 3

[Joey Armstrong [:joey]]

Reopened as a reminder that w64-ix-slave36 needs work.

Comment 4

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

This is actually a known issue in the msys we have on the win32 slaves, which gets confused about 'duplicated inodes' when running on top of NTFS. Apparently it affects win64 too. Short of investigating updating msys the fix is to clobber the build directory in question, and that's happened already. The rate of failure is low, so we haven't put effort into msys.

We can morph this bug for the general fix, or resolve it FIXED because w64-ix-slave36 is fine. I'd advocate the latter.