Closed
Bug 872414
Opened 11 years ago
Closed 11 years ago
controller.restartApplication() gives "IO Completion Port unexpectedly closed" error
Categories
(Testing Graveyard :: Mozmill, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 865690
People
(Reporter: andrei, Unassigned)
Details
Attachments
(1 file)
|
1.28 KB,
text/plain
|
Details |
mozmill 2.0 on windows give the following error:
"IO Completion Port unexpectedly closed"
when using
> controller.restartApplication()
Will have a testcase shortly.
|
Reporter | |
Comment 1•11 years ago
|
||
This shows the error reported (but no disconnect). Trying to see if this actually leads to a Disconnect Error and if so what factors trigger it.
|
||
Updated•11 years ago
|
Attachment #749728 -
Attachment mime type: text/x-patch → text/plain
|
|
||
Comment 2•11 years ago
|
||
Sounds like NSPR is involved here. So for which of those restartApplication() calls does it happen? For all of them?
Whiteboard: [mozmill-2.0?]
|
||
Updated•11 years ago
|
Whiteboard: [mozmill-2.0?] → [mozmill-2.0?][sprint2013-34]
(In reply to Andrei Eftimie from comment #0) > mozmill 2.0 on windows give the following error: > "IO Completion Port unexpectedly closed" > when using > > controller.restartApplication() > > Will have a testcase shortly. The underlying mozprocess code is printing that error[1], which isn't really an error if we shutdown the application when the underlying code didn't expect it. So in other words, this might be expected when doing restartApplication. [1] https://github.com/mozilla/mozbase/blob/master/mozprocess/mozprocess/processhandler.py#L323
|
|
||
Comment 4•11 years ago
|
||
Actually this is a dupe of bug 865690.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Whiteboard: [mozmill-2.0?][sprint2013-34] → [sprint2013-34]
|
|
||
Updated•11 years ago
|
Whiteboard: [sprint2013-34]
|
Assignee | |
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•