897011 - Multiple exceptions during cleanup at the end of green WinXP jetpack test runs ("WindowsError: [Error 32] The process cannot access the file because it is being used by another process" in maybe_remove_outfile)

Status: RESOLVED WORKSFORME

(Add-on SDK Graveyard :: General, defect, P1)

Description

[Ed Morley [:emorley]]

eg:
https://tbpl.mozilla.org/php/getParsedLog.php?id=25601434&tree=Mozilla-Central#error0

Windows XP 32-bit mozilla-central debug test jetpack on 2013-07-23 02:56:34 PDT for push fb4bf993a58a

slave: t-xp32-ix-129

{
--DOMWINDOW == 278 (40725CA0) [serial = 2271] [outer = 00000000] [url = data:text/html;charset=utf-8,<title>tab%202</title>]
--DOMWINDOW == 277 (4036B2C8) [serial = 2265] [outer = 00000000] [url = data:text/html;charset=utf-8,<title>tab%201</title>]
--DOMWINDOW == 276 (3FD49F48) [serial = 2255] [outer = 00000000] [url = about:mozilla]
--DOMWINDOW == 275 (3D7B7358) [serial = 2246] [outer = 00000000] [url = about:blank]
--DOMWINDOW == 274 (3D2C0C68) [serial = 2236] [outer = 00000000] [url = data:text/html;charset=utf-8,<i>testTrackWindows</i>]

8217 of 8217 tests passed.
Error Cleaning up: [Error 5] Access is denied: 'c:\\docume~1\\cltbld~1.t-x\\locals~1\\temp\\tmpj0xc4l.mozrunner\\extensions\\[e-mail]'
Error Cleaning up: [Error 145] The directory is not empty: 'c:\\docume~1\\cltbld~1.t-x\\locals~1\\temp\\tmpj0xc4l.mozrunner\\extensions'
Error Cleaning up: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\docume~1\\cltbld~1.t-x\\locals~1\\temp\\tmpj0xc4l.mozrunner\\parent.lock'
Error Cleaning up: [Error 145] The directory is not empty: 'c:\\docume~1\\cltbld~1.t-x\\locals~1\\temp\\tmpj0xc4l.mozrunner'
Total time: 695.336000 seconds
Program terminated successfully.
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "c:\mozilla-build\python27\Lib\atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "C:\slave\test\build\jetpack\python-lib\cuddlefish\runner.py", line 536, in maybe_remove_outfile
    os.remove(outfile)
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\docume~1\\cltbld~1.t-x\\locals~1\\temp\\harness-stdout-_o55lb'
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "c:\mozilla-build\python27\Lib\atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "C:\slave\test\build\jetpack\python-lib\cuddlefish\runner.py", line 482, in maybe_remove_logfile
    os.remove(logfile)
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\docume~1\\cltbld~1.t-x\\locals~1\\temp\\harness-log-mgnios'
Error in sys.exitfunc:
Traceback (most recent call last):
  File "c:\mozilla-build\python27\Lib\atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "C:\slave\test\build\jetpack\python-lib\cuddlefish\runner.py", line 482, in maybe_remove_logfile
    os.remove(logfile)
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\docume~1\\cltbld~1.t-x\\locals~1\\temp\\harness-log-mgnios'
program finished with exit code 0
elapsedTime=697.678000
TinderboxPrint:jetpack<br/>8217/0
========= Finished 'python jetpack/bin/cfx ...' (results: 0, elapsed: 11 mins, 38 secs) (at 2013-07-23 03:10:05.442629) =========
}

a) Should these fail the run?
b) If so: We should make sure the harness reports an error & fix these.
   If not: We should catch the exception and print an error that won't be picked up by TBPL's parser (to avoid confusion when looking at failed runs that have failed for something unrelated).

Comment 1

[Ed Morley [:emorley]]

(In reply to Ed Morley [:edmorley UTC+1] from comment #0)
> a) Should these fail the run?
> b) If so: We should make sure the harness reports an error & fix these.
>    If not: We should catch the exception and print an error that won't be
> picked up by TBPL's parser (to avoid confusion when looking at failed runs
> that have failed for something unrelated).

Comment 2

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

(In reply to Ed Morley [:edmorley UTC+1] from comment #1)
> (In reply to Ed Morley [:edmorley UTC+1] from comment #0)
> > a) Should these fail the run?
> > b) If so: We should make sure the harness reports an error & fix these.
> >    If not: We should catch the exception and print an error that won't be
> > picked up by TBPL's parser (to avoid confusion when looking at failed runs
> > that have failed for something unrelated).

Unsure. Passing the question over to Dave.

Comment 3

[Dave Townsend [:mossop]]

Probably they should be test failures, much as I'd like them not to be. My hope is that switching to a recent mozrunner will solve these.

Comment 4

[Ed Morley [:emorley]]

Seems to have gone away on trunk.