Closed Bug 1474951 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 11914 - Streams: pipeTo error flushing pending writes test

Categories

(Core :: DOM: Core & HTML, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 11914 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/11914 Details from upstream follow. Adam Rice <ricea@chromium.org> wrote: > Streams: pipeTo error flushing pending writes test > > Add a test for what happens when an error occurs flushing pending writes in > pipeTo after the readable closes. > > This clarifies behaviour that is not obvious from the standard. > > Related to whatwg/streams#939
Component: web-platform-tests → DOM
Product: Testing → Core
Ran 4 tests and 121 subtests OK : 4 PASS : 1 FAIL : 120 New tests that have failures or other problems: /streams/piping/close-propagation-forward.dedicatedworker.html Closing must be propagated forward: erroring the writable while flushing pending writes should error pipeTo: FAIL /streams/piping/close-propagation-forward.html Closing must be propagated forward: erroring the writable while flushing pending writes should error pipeTo: FAIL /streams/piping/close-propagation-forward.serviceworker.https.html Closing must be propagated forward: erroring the writable while flushing pending writes should error pipeTo: FAIL /streams/piping/close-propagation-forward.sharedworker.html Closing must be propagated forward: erroring the writable while flushing pending writes should error pipeTo: FAIL
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/adcf20a9b003 [wpt PR 11914] - Streams: pipeTo error flushing pending writes test, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/2bf1256d21f6 [wpt PR 11914] - Update wpt metadata, a=testonly
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.