Closed Bug 1496589 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 13358 - [streams] Add tests for aborting pipeTo()

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla65
Tracking Flags:
Tracking Status
firefox65 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 13358 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/13358 Details from upstream follow. Adam Rice <ricea@chromium.org> wrote: > [streams] Add tests for aborting pipeTo() > > Add tests for aborting ReadableStream.prototype.pipeTo using an > AbortSignal. > > Tests correspond to PR whatwg/streams#744.
Component: web-platform-tests → DOM
Product: Testing → Core
Ran 4 tests and 89 subtests OK : 4 PASS : 1 FAIL : 88 New tests that have failures or other problems: /streams/piping/abort.dedicatedworker.html a rejection from underlyingSink.abort() should be preferred to one from underlyingSource.cancel(): FAIL a rejection from underlyingSink.abort() should be returned by pipeTo(): FAIL a rejection from underlyingSource.cancel() should be returned by pipeTo(): FAIL a signal argument '-1' should cause pipeTo() to reject: FAIL a signal argument 'AbortSignal' should cause pipeTo() to reject: FAIL a signal argument '[object Object]' should cause pipeTo() to reject: FAIL a signal argument 'null' should cause pipeTo() to reject: FAIL a signal argument 'true' should cause pipeTo() to reject: FAIL abort should do nothing after the readable is closed: FAIL abort should do nothing after the readable is errored: FAIL abort should do nothing after the readable is errored, even with pending writes: FAIL abort should do nothing after the writable is errored: FAIL abort should prevent further reads: FAIL abort signal takes priority over closed readable: FAIL abort signal takes priority over closed writable: FAIL abort signal takes priority over errored readable: FAIL abort signal takes priority over errored writable: FAIL all pending writes should complete on abort: FAIL all the AbortError objects should be the same object: FAIL an aborted signal should cause the writable stream to reject with an AbortError: FAIL preventAbort should prevent aborting the readable: FAIL preventCancel should prevent canceling the readable: FAIL /streams/piping/abort.html a rejection from underlyingSink.abort() should be preferred to one from underlyingSource.cancel(): FAIL a rejection from underlyingSink.abort() should be returned by pipeTo(): FAIL a rejection from underlyingSource.cancel() should be returned by pipeTo(): FAIL a signal argument '-1' should cause pipeTo() to reject: FAIL a signal argument 'AbortSignal' should cause pipeTo() to reject: FAIL a signal argument '[object Object]' should cause pipeTo() to reject: FAIL a signal argument 'null' should cause pipeTo() to reject: FAIL a signal argument 'true' should cause pipeTo() to reject: FAIL abort should do nothing after the readable is closed: FAIL abort should do nothing after the readable is errored: FAIL abort should do nothing after the readable is errored, even with pending writes: FAIL abort should do nothing after the writable is errored: FAIL abort should prevent further reads: FAIL abort signal takes priority over closed readable: FAIL abort signal takes priority over closed writable: FAIL abort signal takes priority over errored readable: FAIL abort signal takes priority over errored writable: FAIL all pending writes should complete on abort: FAIL all the AbortError objects should be the same object: FAIL an aborted signal should cause the writable stream to reject with an AbortError: FAIL preventAbort should prevent aborting the readable: FAIL preventCancel should prevent canceling the readable: FAIL /streams/piping/abort.serviceworker.https.html a rejection from underlyingSink.abort() should be preferred to one from underlyingSource.cancel(): FAIL a rejection from underlyingSink.abort() should be returned by pipeTo(): FAIL a rejection from underlyingSource.cancel() should be returned by pipeTo(): FAIL a signal argument '-1' should cause pipeTo() to reject: FAIL a signal argument 'AbortSignal' should cause pipeTo() to reject: FAIL a signal argument '[object Object]' should cause pipeTo() to reject: FAIL a signal argument 'null' should cause pipeTo() to reject: FAIL a signal argument 'true' should cause pipeTo() to reject: FAIL abort should do nothing after the readable is closed: FAIL abort should do nothing after the readable is errored: FAIL abort should do nothing after the readable is errored, even with pending writes: FAIL abort should do nothing after the writable is errored: FAIL abort should prevent further reads: FAIL abort signal takes priority over closed readable: FAIL abort signal takes priority over closed writable: FAIL abort signal takes priority over errored readable: FAIL abort signal takes priority over errored writable: FAIL all pending writes should complete on abort: FAIL all the AbortError objects should be the same object: FAIL an aborted signal should cause the writable stream to reject with an AbortError: FAIL preventAbort should prevent aborting the readable: FAIL preventCancel should prevent canceling the readable: FAIL /streams/piping/abort.sharedworker.html a rejection from underlyingSink.abort() should be preferred to one from underlyingSource.cancel(): FAIL a rejection from underlyingSink.abort() should be returned by pipeTo(): FAIL a rejection from underlyingSource.cancel() should be returned by pipeTo(): FAIL a signal argument '-1' should cause pipeTo() to reject: FAIL a signal argument 'AbortSignal' should cause pipeTo() to reject: FAIL a signal argument '[object Object]' should cause pipeTo() to reject: FAIL a signal argument 'null' should cause pipeTo() to reject: FAIL a signal argument 'true' should cause pipeTo() to reject: FAIL abort should do nothing after the readable is closed: FAIL abort should do nothing after the readable is errored: FAIL abort should do nothing after the readable is errored, even with pending writes: FAIL abort should do nothing after the writable is errored: FAIL abort should prevent further reads: FAIL abort signal takes priority over closed readable: FAIL abort signal takes priority over closed writable: FAIL abort signal takes priority over errored readable: FAIL abort signal takes priority over errored writable: FAIL all pending writes should complete on abort: FAIL all the AbortError objects should be the same object: FAIL an aborted signal should cause the writable stream to reject with an AbortError: FAIL preventAbort should prevent aborting the readable: FAIL preventCancel should prevent canceling the readable: FAIL
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/d3eedf1cb5de [wpt PR 13358] - [streams] Add tests for aborting pipeTo(), a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/f62c286c68dd [wpt PR 13358] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/d3eedf1cb5de https://hg.mozilla.org/mozilla-central/rev/f62c286c68dd
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox65: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.