Crashtest red on talos-r3-w7-037 with " rm: cannot remove directory `build/xpcshell/tests/xpcom/tests/unit': Directory not empty" after suite has completed

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: dholbert, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildduty], URL)

https://tbpl.mozilla.org/php/getParsedLog.php?id=10025738&tree=Mozilla-Inbound
Rev3 WINNT 6.1 mozilla-inbound opt test crashtest on 2012-03-13 00:59:14 PDT for push d4496bf4bb64
builder: mozilla-inbound_win7_test-crashtest
slave: talos-r3-w7-037
starttime: 1331625554.67
results: failure (2)
buildid: 20120312230409
builduid: 099d6c47c44f477389c83c8c5ad120da
revision: d4496bf4bb64

Snippet from log (this is just after the actual crashtest part has completed succesfully):
{
========= Started 'rm -rf ...' failed (results: 2, elapsed: 34 secs) ==========
'rm' '-rf' 'build'
 in dir c:\talos-slave\test\. (timeout 1200 secs)
 watching logfiles {}
 argv: ['rm', '-rf', 'build']
 environment:
  ALLUSERSPROFILE=C:\ProgramData
  APPDATA=C:\Users\cltbld\AppData\Roaming
  COMMONPROGRAMFILES=C:\Program Files\Common Files
  COMPUTERNAME=TALOS-R3-W7-037
  COMSPEC=C:\Windows\system32\cmd.exe
  FP_NO_HOST_CHECK=NO
  HOMEDRIVE=C:
  HOMEPATH=\Users\cltbld
  LOCALAPPDATA=C:\Users\cltbld\AppData\Local
  LOGONSERVER=\\TALOS-R3-W7-037
  MOZ_CRASHREPORTER_NO_REPORT=1
  MOZ_NO_REMOTE=1
  NO_EM_RESTART=1
  NUMBER_OF_PROCESSORS=2
  OS=Windows_NT
  PATH=C:\mozilla-build;C:\mozilla-build\msys\bin;C:\mozilla-build\msys\local\bin;C:\mozilla-build\buildbotve\scripts;C:\mozilla-build\Python25;C:\mozilla-build\Python25\Scripts;C:\mozilla-build\hg;C:\mozilla-build\7zip;C:\mozilla-build\upx203w;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32;C:\WINDOWS;
  PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
  PROCESSOR_ARCHITECTURE=x86
  PROCESSOR_IDENTIFIER=x86 Family 6 Model 23 Stepping 10, GenuineIntel
  PROCESSOR_LEVEL=6
  PROCESSOR_REVISION=170a
  PROGRAMDATA=C:\ProgramData
  PROGRAMFILES=C:\Program Files
  PROMPT=$P$G
  PSMODULEPATH=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
  PUBLIC=C:\Users\Public
  PWD=c:\talos-slave\test
  SYSTEMDRIVE=C:
  SYSTEMROOT=C:\Windows
  TEMP=C:\Users\cltbld\AppData\Local\Temp
  TMP=C:\Users\cltbld\AppData\Local\Temp
  USERDOMAIN=TALOS-R3-W7-037
  USERNAME=cltbld
  USERPROFILE=C:\Users\cltbld
  WINDIR=C:\Windows
  XPCOM_DEBUG_BREAK=warn
 using PTY: False
rm: cannot remove directory `build/xpcshell/tests/xpcom/tests/unit': Directory not empty
program finished with exit code 1
elapsedTime=29.201000
======== Finished 'rm -rf ...' failed (results: 2, elapsed: 34 secs) ========
}
So "rm -fr" is failing to remove a directory because that directory is nonempty.

That makes no sense. (it's supposed to recursively remove directories)

I'm guessing there might be filesystem corruption or a locked file or something...?
It's an msys problem or a file still in use for a split of a second.
See bug 692715. There are various solution but we have not had time to get to it.
Removed manually and put back into the pool.

C:\talos-slave>rm -rf test\build
rm: reading directory `test\\build/xpcshell/tests/xpcom/tests/unit': Invalid arg
ument
rm: cannot remove directory `test\\build/xpcshell/tests/xpcom/tests': Directory
not empty

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

C:\talos-slave>rm -rf test\build
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Whiteboard: [buildduty]
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.