Intermittent test_switch_frame.py TestSwitchFrame.test_should_be_able_to_switch_to_a_frame_by_its_index | IOError: Process has been unexpectedly closed (Exit code: 0) (Reason: Connection timed out after 65.0s)

RESOLVED FIXED in Firefox 52

Status

Testing
Marionette
RESOLVED FIXED
9 months ago
8 months ago

People

(Reporter: Treeherder Bug Filer, Assigned: whimboo)

Tracking

({intermittent-failure})

Version 3
mozilla54
intermittent-failure
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox52 fixed, firefox53 fixed, firefox54 fixed)

Details

(Reporter)

Description

9 months ago
treeherder
Filed by: hskupin [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=72057146&repo=autoland

https://queue.taskcluster.net/v1/task/CE6KdBwaRhOhNfJYdHCfjA/runs/0/artifacts/public/logs/live_backing.log
(Assignee)

Comment 1

9 months ago
The hang here happens in navigate(), specifically to our locally served page "frameset.html".

Maybe bug 1334149 can help us here.
Depends on: 1334149

Comment 2

9 months ago
20 failures in 749 pushes (0.027 failures/push) were associated with this bug in the last 7 days.  

Repository breakdown:
* autoland: 20

Platform breakdown:
* android-4-3-armv7-api15: 20

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1334033&startday=2017-01-23&endday=2017-01-29&tree=all

Comment 3

9 months ago
9 failures in 733 pushes (0.012 failures/push) were associated with this bug in the last 7 days.  

Repository breakdown:
* autoland: 9

Platform breakdown:
* android-4-3-armv7-api15: 9

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1334033&startday=2017-01-30&endday=2017-02-05&tree=all
(Assignee)

Comment 4

8 months ago
This is fixed now since the patch on bug 1322277 landed.
Status: NEW → RESOLVED
Last Resolved: 8 months ago
status-firefox54: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
Assignee: nobody → hskupin
status-firefox52: --- → fixed
status-firefox53: --- → fixed
You need to log in before you can comment on or make changes to this bug.