Argh, I checked SeaMonkey 2.1 tinderboxes: *unaffected: build, crashtest, reftest :-| *fixed: leak, xpcshell :-) *not fixed: mochitests, mochitest-other :-( { JS Component Loader: ERROR (null):0 uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: file:///builds/slave/comm-central-trunk-macosx-debug-unittest-mochitest-other/build/SeaMonkeyDebug.app/Contents/MacOS/components/msgAsyncPrompter.js :: <TOP_LEVEL> :: line 39" data: no] JS Component Loader: ERROR (null):0 uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getIntPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: file:///builds/slave/comm-central-trunk-macosx-debug-unittest-mochitest-other/build/SeaMonkeyDebug.app/Contents/MacOS/components/nsMsgTraitService.js :: _init :: line 239" data: no] JS Component Loader: ERROR (null):0 uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: file:///builds/slave/comm-central-trunk-macosx-debug-unittest-mochitest-other/build/SeaMonkeyDebug.app/Contents/MacOS/components/nsSuiteGlue.js :: <TOP_LEVEL> :: line 45" data: no] } Something wrong with the mochitest harness? Related to package-tests??

Are you seeing this on all platforms? I wonder if a clobber is enough to clear this up (even though clobbering is a lot of work until we get to fix bug 555449).

(In reply to comment #1) Yes, this bug is filed as All+All. I wondered the same thing, but in this case I couldn't image how a clobber (on the builder) would help. And I assume a clobber is already run on the test runner. (Yet, it should not matter either in this case, should it?) Still, if you think it's worth a try, please do. (I've no clue atm.)

I have clobbered all the Windows build because I thought the burning there could be caused by left-over files (but it looks like it wasn't). If this still is happening on Windows tests from builds after that red clears up, then a clobber doesn't help, which is what I'd suspect (but I'm never 100% sure).

Serge I'm going to close this RSN unless you tell me that this is still occurring.

I did a brief search on all Windows logs and couldn't find these failures anymore. I am sorry it took so long :-/

(In reply to Serge Gautherie (:sgautherie) from comment #5) > all Windows logs on SM 2.12a1.