Closed Bug 1189656 Opened 5 years ago Closed 5 years ago

"Harness status: Timeout" when running "fetch-request-fallback.https.html" test

Categories

(Testing :: web-platform-tests, defect)

defect
Not set
normal

Tracking

(firefox42 affected, firefox43 fixed)

RESOLVED FIXED
mozilla43
Tracking Status
firefox42 --- affected
firefox43 --- fixed

People

(Reporter: noemi, Assigned: nsm)

References

Details

Attachments

(1 file)

Test run such as |./mach web-platform-tests _mozilla/service-workers/service-worker/fetch-request-fallback.https.html|

Actual Result:
Harness status: Timeout
Found 1 tests
1 Timeout
* Verify the fallback behavior of FetchEvent -> timed out
Traces: https://pastebin.mozilla.org/8838595
Bug 1189656 - Fix fetch-request-fallback test paths. r?bkelly

This still leads to the test failing since navigation of the original iframe
should have mode no-cors instead of same-origin.
Update web-platform-tests expected data
Attachment #8659564 - Flags: review?(bkelly)
Navigation's always have same-origin RequestMode now.  There is a note in the fetch spec.
Comment on attachment 8659564 [details]
MozReview Request: Bug 1189656 - Fix fetch-request-fallback test paths. r?bkelly

Bug 1189656 - Fix fetch-request-fallback test paths. r?bkelly

Update web-platform-tests expected data
Comment on attachment 8659564 [details]
MozReview Request: Bug 1189656 - Fix fetch-request-fallback test paths. r?bkelly

https://reviewboard.mozilla.org/r/18953/#review16861
Attachment #8659564 - Flags: review?(bkelly) → review+
Patch provided by Nikhil so assigning this to him. Please feel free to change it as needed. Thanks!
Assignee: nobody → nsm.nikhil
Status: NEW → ASSIGNED
https://hg.mozilla.org/mozilla-central/rev/d1294ebe0e3b
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
Hi,

just checked in  m-c (c69e31de9aec revision) and the test successfully runs. Thanks for fixing it!.

Summary

Harness status: OK

Found 1 tests
1 Pass
Details
Result	Test Name
Pass	Verify the fallback behavior of FetchEvent
You need to log in before you can comment on or make changes to this bug.