Closed
Bug 1051683
Opened 11 years ago
Closed 3 years ago
Intermittent (?) WinNT comm-beta mochitest giving a "The handle is invalid" Windows error.
Categories
(SeaMonkey :: Release Engineering, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ewong, Unassigned)
Details
Getting this during a mochitest-plain-4 build:
(It also happened to mochitest-plain-5, but it seems to have corrected itself.
(It looks intermittent.)
INFO | runtests.py | Application pid: 3420
TEST-UNEXPECTED-FAIL | automation.py | application timed out after 330 seconds with no output
Failed to retrieve MOZ_UPLOAD_DIR env var
TEST-INFO | crashinject: exit status 0
[1276] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file e:/builds/slave/c-beta-w32-dbg/build/mozilla/toolkit/components/places/Database.cpp, line 449
[1276] WARNING: NS_ENSURE_TRUE(mDB) failed: file e:/builds/slave/c-beta-w32-dbg/build/mozilla/toolkit/components/places/nsNavHistory.cpp, line 296
System JS : ERROR resource://gre/modules/FormHistory.jsm:377 - NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIProperties.get]
[1276] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file e:/builds/slave/c-beta-w32-dbg/build/mozilla/toolkit/components/places/Database.cpp, line 449
[1276] WARNING: NS_ENSURE_TRUE(mDB) failed: file e:/builds/slave/c-beta-w32-dbg/build/mozilla/toolkit/components/places/nsNavHistory.cpp, line 296
Automation Error: Received unexpected exception while running application
Stopping web server
Stopping web socket server
Stopping ssltunnel
WARNING | leakcheck | refcount logging is off, so leaks can't be detected!
runtests.py | Running tests: end.
Traceback (most recent call last):
File "mochitest/runtests.py", line 1471, in doTests
testPath=options.testPath
File "mochitest/runtests.py", line 1286, in runApp
status = proc.wait()
File "e:\builds\slave\test\build\mozbase\mozprocess\mozprocess\processhandler.py", line 824, in wait
return self.proc.wait()
File "e:\builds\slave\test\build\mozbase\mozprocess\mozprocess\processhandler.py", line 162, in wait
self.returncode = self._wait()
File "e:\builds\slave\test\build\mozbase\mozprocess\mozprocess\processhandler.py", line 462, in _wait
raise OSError(err)
OSError: IO Completion Port failed to signal process shutdown
Error Code 6 trying to query IO Completion Port, exiting
Exception in thread Thread-23:
Traceback (most recent call last):
File "D:\mozilla-build\python27\lib\threading.py", line 551, in __bootstrap_inner
self.run()
File "D:\mozilla-build\python27\lib\threading.py", line 504, in run
self.__target(*self.__args, **self.__kwargs)
File "e:\builds\slave\test\build\mozbase\mozprocess\mozprocess\processhandler.py", line 321, in _procmgr
self._poll_iocompletion_port()
File "e:\builds\slave\test\build\mozbase\mozprocess\mozprocess\processhandler.py", line 371, in _poll_iocompletion_port
raise WinError(errcode)
WindowsError: [Error 6] The handle is invalid.
command timed out: 1200 seconds without output, attempting to kill
SIGKILL failed to kill process
using fake rc=-1
program finished with exit code -1
remoteFailed: [Failure instance: Traceback from remote host -- Traceback (most recent call last):
Failure: exceptions.RuntimeError: SIGKILL failed to kill process
]
| Reporter | ||
Updated•11 years ago
|
Summary: Intermittent (?) WinNT comm-beta mochitest - 4 is giving a "The handle is invalid" Windows error. → Intermittent (?) WinNT comm-beta mochitest giving a "The handle is invalid" Windows error.
| Reporter | ||
Comment 1•3 years ago
|
||
We no longer use comm-beta. So closing.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•