Closed Bug 1320642 Opened 8 years ago Closed 8 years ago

Permafail test_places.py TestPlaces.test_bookmarks | IOError: Process has been unexpectedly closed (Exit code: -15) (Reason: [Errno 111] Connection refused)

Categories

(Testing :: Firefox UI Tests, defect)

Product:
Testing
Component:
Firefox UI Tests
Version:
Version 3
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(firefox51 unaffected, firefox52 fixed, firefox53 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla53
Tracking Flags:
Tracking Status
firefox51 --- unaffected
firefox52 --- fixed
firefox53 --- fixed

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure) 

Happened for all en-US Nightly builds yesterday for OS X and Linux when we call navigate():

06:24:58     INFO -  1480256698242	Marionette	TRACE	conn14 -> [0,50,"get",{"url":"http://10.22.73.172:40881/layout/mozilla_governance.html"}]
06:25:58     INFO -  1480256758302	Marionette	DEBUG	Closed connection conn14
06:27:04     INFO - TEST-UNEXPECTED-ERROR | test_places.py TestPlaces.test_bookmarks | IOError: Process has been unexpectedly closed (Exit code: -15) (Reason: [Errno 111] Connection refused)

As you can see in the host ip the local test pages we no longer serve via 127.0.0.1 but through the public IP of the host. I strongly believe that this and the abort of Firefox is a regression from bug 1103196 which landed earlier on Sunday.
Blocks: 1103196
Flags: needinfo?(ato)
I have filed the public IP part under Marionette as bug 1320643.
Depends on: 1320643
(In reply to Henrik Skupin (:whimboo) from comment #1)
> As you can see in the host ip the local test pages we no longer serve via
> 127.0.0.1 but through the public IP of the host. I strongly believe that
> this and the abort of Firefox is a regression from bug 1103196 which landed
> earlier on Sunday.

That it’s intermittent suggests the assert isn’t deterministic.
Flags: needinfo?(ato)
As I have said in comment 0 this is a hang in navigate/get and most likely related to your httpd changes. I will wait for todays Nightly builds but so far it seems to be a perma failure for those builds on Linux and OS X.
It's actually not the only test which is failing on OS X nightly builds permanently. Here an example:

https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=Firefox%20&filter-tier=1&filter-tier=2&filter-tier=3&bugfiler&selectedJob=5715589
Severity: normal → major
Summary: Intermittent test_places.py TestPlaces.test_bookmarks | IOError: Process has been unexpectedly closed (Exit code: -15) (Reason: [Errno 111] Connection refused) → Permafail test_places.py TestPlaces.test_bookmarks | IOError: Process has been unexpectedly closed (Exit code: -15) (Reason: [Errno 111] Connection refused)
I discovered that the underlying problem here is a missing noproxy setting for our Linux and Mac machines for `10.*.*.*`, which is the local network the machines run in. I will have to get this added and the timeout for navigate() with 300s will not cause our jobs to get hard-killed after 60 minutes.
Depends on: 1322199
Given that the underlying proxy is not configured correctly, a page load for a locally served page will not timeout but interrupted by a socket timeout. Reason is that the latter kicks in after 60s, and a call to get() will return after its default timeout of 300s. As such we see this failure.

I proposed to dynamically adjust the socket timeout based on the expected command duration over on bug 1322277.
Depends on: 1322277
Fixed by bug 1322199 which includes the Proxy updates for our Linux and OS X machines. Beside that bug 1320643 would also have fixed the failure.
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox52: --- → fixed
status-firefox53: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
You need to log in before you can comment on or make changes to this bug.