Closed Bug 1095652 Opened 11 years ago Closed 8 years ago

Test failure "Disconnect Error: Application unexpectedly closed" in testUpdate.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)

Version 2
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: lizzard, Unassigned)

References

Details

This update test failed this morning, http://mozmill-release.blargon7.com/#/update/report/43b0604030afed1afa485902873dbb04 from the console log: http://mm-ci-master.qa.scl3.mozilla.com:8080/job/ondemand_update/103897/console 11:13:00 Parent process 3692 exited with children alive: 11:13:00 PIDS: 4044 11:13:00 Attempting to kill them... 11:13:01 RESULTS | Passed: 2 11:13:01 RESULTS | Failed: 1 11:13:01 RESULTS | Skipped: 0 11:13:35 Report document created at 'http://mozauto.iriscouch.com/mozmill-release/43b0604030afed1afa485902873dbb04' 11:13:35 *** Removing profile: c:\jenkins\workspace\ondemand_update\data\profile 11:13:35 *** Uninstalling build: c:\jenkins\workspace\ondemand_update\data\binary\firefox-33 11:16:30 Exception in thread Thread-5: 11:16:30 Traceback (most recent call last): 11:16:30 File "c:\jenkins\workspace\ondemand_update\mozmill-env-windows\python\Lib\threading.py", line 808, in __bootstrap_inner 11:16:30 self.run() 11:16:30 File "c:\jenkins\workspace\ondemand_update\mozmill-env-windows\python\Lib\threading.py", line 761, in run 11:16:30 self.__target(*self.__args, **self.__kwargs) 11:16:30 File "c:\jenkins\workspace\ondemand_update\mozmill-env-windows\python\lib\site-packages\mozprocess\processhandler.py", line 322, in _procmgr 11:16:30 self._poll_iocompletion_port() 11:16:30 File "c:\jenkins\workspace\ondemand_update\mozmill-env-windows\python\lib\site-packages\mozprocess\processhandler.py", line 357, in _poll_iocompletion_port 11:16:30 self.kill() 11:16:30 File "c:\jenkins\workspace\ondemand_update\mozmill-env-windows\python\lib\site-packages\mozprocess\processhandler.py", line 142, in kill 11:16:30 self.returncode = self.wait() 11:16:30 File "c:\jenkins\workspace\ondemand_update\mozmill-env-windows\python\lib\site-packages\mozprocess\processhandler.py", line 163, in wait 11:16:30 self.returncode = self._wait() 11:16:30 File "c:\jenkins\workspace\ondemand_update\mozmill-env-windows\python\lib\site-packages\mozprocess\processhandler.py", line 463, in _wait 11:16:30 raise OSError(err) 11:16:30 OSError: IO Completion Port failed to signal process shutdown 11:16:30 11:17:23 *** Removing test repository 'c:\jenkins\workspace\ondemand_update\data\mozmill-tests' 11:17:29 Build step 'Invoke XShell command' marked build as failure 11:17:29 Archiving artifacts
I saw this failure in many runs today, across several Windows machines.
(In reply to Mihaela Velimiroviciu [QA] (:mihaelav) from comment #1) > I saw this failure in many runs today, across several Windows machines. How big is the impact? If it doesn't every time, but the number is significant, that's probably a P2. Does this fail only on Windows? Are specific versions affected?
(In reply to Andrei Eftimie from comment #2) > (In reply to Mihaela Velimiroviciu [QA] (:mihaelav) from comment #1) > > I saw this failure in many runs today, across several Windows machines. > > How big is the impact? > > If it doesn't every time, but the number is significant, that's probably a > P2. It doesn't happen every time. Sometimes it works at a rebuild, sometimes it doesn't and from what I've seen so far, it keeps failing on mm-win-xp-32-1 on mm-win-81-32-3. I'll take those 2 machines offline for investigation > Does this fail only on Windows? Yes, I only saw this on windows > Are specific versions affected? It reproduced across all versions: xp, 7, 8, 8.1...
Priority: -- → P2
Depends on: 1351343
Mozmill is dead. So this is nothing we have to worry about anymore.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.