Closed Bug 1295889 Opened 9 years ago Closed 9 years ago

Intermittent test_screenshot.py Chrome.test_secondary_windows | IOError: Process killed because the connection to Marionette server is lost. Check gecko.log for errors (Reason: Connection timed out after 360s)

Categories

(Testing :: Marionette Client and Harness, defect)

Version 3
defect
Not set
normal

Tracking

(firefox51 fixed)

RESOLVED FIXED
mozilla51
Tracking Status
firefox51 --- fixed

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [blocked by bug 1294456])

Here an excerpt from the gecko.log: m64-d-0000000000000000/build/src/embedding/components/windowwatcher/nsWindowWatcher.cpp, line 2186 ++DOMWINDOW == 180 (0x12e609400) [pid = 1659] [serial = 609] [outer = 0x12d756800] 1471396903193 Marionette TRACE conn904 <- [1,9,null,{"value":null}] ++DOMWINDOW == 181 (0x12cdf1c00) [pid = 1659] [serial = 610] [outer = 0x12d756800] 1471396903497 Marionette TRACE conn904 -> [0,10,"getChromeWindowHandles",null] 1471396903499 Marionette TRACE conn904 <- [1,10,null,["3","601"]] 1471396903506 Marionette TRACE conn904 -> [0,11,"getChromeWindowHandles",null] 1471396903508 Marionette TRACE conn904 <- [1,11,null,["3","601"]] 1471396903511 Marionette TRACE conn904 -> [0,12,"switchToWindow",{"name":"601"}] 1471396903575 Marionette DEBUG loaded listener.js 1471397263532 Marionette DEBUG Closed connection conn904 As you can see we send the switchToWindow() command at 1471396903511 and never get a reponse. Then we close the socket connection 360s later. It looks to be similar to bug 1294456.
Depends on: 1294456
This should no longer be an issue since the patch on bug 1294456 has been landed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [blocked by bug 1294456]
Target Milestone: --- → mozilla51
Product: Testing → Remote Protocol
Moving bug to Testing::Marionette Client and Harness component per bug 1815831.
Component: Marionette → Marionette Client and Harness
Product: Remote Protocol → Testing
You need to log in before you can comment on or make changes to this bug.