Closed Bug 1492512 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 13079 - [Background Fetch] Set bad-status as failureReason

Categories

(Core :: DOM: Service Workers, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla64
Tracking Status
firefox64 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 13079 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/13079 Details from upstream follow. Mugdha Lakhani <nator@chromium.org> wrote: > [Background Fetch] Set bad-status as failureReason > > when one of the settled fetches has a response with a bad status. > > Bug: 876691 > Change-Id: I45af6b792a6a43e5b091bc5fe6f40d011bdabac5 > Reviewed-on: https://chromium-review.googlesource.com/1233693 > WPT-Export-Revision: 21023276fd48724d966e60b3b96e9d9db02f5402
PR 13079 applied with additional changes from upstream: 445544dcf920e46d158bfe82b1e45e30360ed278
Component: web-platform-tests → DOM: Service Workers
Product: Testing → Core
PR 13079 applied with additional changes from upstream: 8abd5d0c3f43ebd83c533e6ac096686879183bd8
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 3 tests and 14 subtests OK : 3 FAIL : 14 New tests that have failures or other problems: /background-fetch/fetch.https.window.html Using Background Fetch to fetch a non-existent resource should fail.: FAIL
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/287c0f441c0b [wpt PR 13079] - [Background Fetch] Set bad-status as failureReason, a=testonly
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in before you can comment on or make changes to this bug.