Closed
Bug 1379065
Opened 8 years ago
Closed 7 years ago
Intermittent test_quit_restart.py TestQuitRestart.test_force_restart | IOError: Process killed because the connection to Marionette server is lost. Check gecko.log for errors (Reason: Timed out waiting for connection on localhost:2828!)
Categories
(Testing :: Marionette Client and Harness, defect, P5)
Tracking
(firefox55 affected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
Details
(Keywords: bulk-close-intermittents, intermittent-failure)
Comment 1•8 years ago
|
||
This is a test failure in headless mode. Not sure if the following warnings are related or if the additional overlapping incoming connection for Marionette is the reason:
1499379986069 Marionette TRACE 3 <- [1,15,null,{}]
*** You are running in headless mode.
*** You are running in headless mode.
(firefox:2549): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
(firefox:2549): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
(firefox:2549): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
1499380178722 Marionette INFO Listening on port 2828
1499380178812 Marionette DEBUG Accepted connection 0 from 127.0.0.1:49020
1499380178849 Marionette DEBUG Accepted connection 1 from 127.0.0.1:49021
1499380178852 Marionette DEBUG Closed connection 0
1499380178857 Marionette TRACE 1 -> [0,1,"newSession",{"sessionId":null,"capabilities":null}]
1499380178867 Marionette CONFIG Matched capabilities: {"browserName":"firefox","browserVersion":"55.0","platformName":"linux","platformVersion":"3.13.0-112-generic","pageLoadStrategy":"normal","acceptInsecureCerts":false,"timeouts":{"implicit":0,"pageLoad":300000,"script":30000},"rotatable":false,"specificationLevel":0,"moz:processID":2549,"moz:profile":"/tmp/tmpEbbfn5.mozrunner","moz:accessibilityChecks":false}
JavaScript error: chrome://marionette/content/server.js, line 337: NS_ERROR_SOCKET_ADDRESS_IN_USE: Component returned failure code: 0x804b0036 (NS_ERROR_SOCKET_ADDRESS_IN_USE) [nsIServerSocket.initSpecialConnection]
Brendan, any idea regarding the dbus warnings?
status-firefox55:
--- → affected
Flags: needinfo?(bdahl)
Comment hidden (Intermittent Failures Robot) |
Comment 3•8 years ago
|
||
I've seen the dbus warnings happen locally and they don't seem to be an issue since they are from some telemetry calls (see bug 1368211). This test failure looks like the previous run of firefox didn't fully shutdown and close all its connections. Given the very low failure rate, I think we need to wait and see if this is actually a headless issue or a general shutdown issue.
Flags: needinfo?(bdahl)
Comment 4•8 years ago
|
||
We had bug 1374043 which was fixed recently and which caused a slow down issue when shutting down Firefox as reported on several bugs in the depencency list. Maybe that's somewhat related. Lets see.
Comment 5•8 years ago
|
||
Whereby this crash is beta only so far...
Comment 6•8 years ago
|
||
With more logging in Marionette we have more information here:
02:52:18 INFO - *** You are running in headless mode.
02:52:18 INFO - 1500432738433 Marionette DEBUG Received observer notification "profile-after-change"
02:52:18 INFO - 1500432738481 Marionette DEBUG Received observer notification "command-line-startup"
02:52:18 INFO - 1500432738481 Marionette INFO Enabled via --marionette
02:55:24 ERROR - TEST-UNEXPECTED-ERROR | test_quit_restart.py TestQuitRestart.test_force_restart | IOError: Process killed because the connection to Marionette server is lost. Check gecko.log for errors (Reason: Timed out waiting for connection on localhost:2828!)
So there is no notification for 'sessionstore-windows-restored' within 3 minutes, which we need to initialize Marionette.
I will file a new bug to specifically handle that.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Keywords: bulk-close-intermittents
Resolution: --- → INCOMPLETE
Comment 10•7 years ago
|
||
Recent failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=163143487&repo=autoland&lineNumber=32320
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Updated•7 years ago
|
Priority: -- → P5
Version: Version 3 → Trunk
Updated•7 years ago
|
OS: Unspecified → Windows
Hardware: Unspecified → x86_64
Comment hidden (Intermittent Failures Robot) |
Comment 12•7 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Comment hidden (Intermittent Failures Robot) |
Comment 14•7 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → INCOMPLETE
Updated•2 years ago
|
Product: Testing → Remote Protocol
Comment 16•2 years ago
|
||
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.
Description
•