Closed Bug 1213119 Opened 10 years ago Closed 10 years ago

Intermittent w-e10s fetch-frame-resource.https.html | Basic type response could be loaded in the iframe. - assert_unreached: unexpected rejection: result is null Reached unreachable code

Categories

(Core :: DOM: Service Workers, defect)

Product:
Core
Component:
DOM: Service Workers
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla45
Tracking Flags:
Tracking Status
e10s + ---
firefox45 --- fixed

People

(Reporter: KWierso, Assigned: bkelly)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Lengthen timeout in test checking for failure to load iframes and windows. r=ehsan
2.62 KB, patch
ehsan.akhgari
: review+
Details | Diff | Splinter Review
Blocks: e10s-tests
tracking-e10s: --- → +
Blocks: 1227687
All of these failures on debug. This test uses a timeout to detect when an iframe has loaded. I believe we're just running slow enough in debug builds that this timeout value is marginal. This patch bumps up the timeout value. Unfortunately there is no way in the API to detect frame/window load failure we can use instead. https://treeherder.mozilla.org/#/jobs?repo=try&revision=a798a12f6891
Assignee: nobody → bkelly
Status: NEW → ASSIGNED
Attachment #8697467 - Flags: review?(ehsan)
Attachment #8697467 - Flags: review?(ehsan) → review+
https://hg.mozilla.org/mozilla-central/rev/4e72112da858
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox45: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: