kitesurf · WPT

FAIL
expected FAIL · 3402 ms
▶ run in kitesurf
Test
/streams/writable-streams/aborting.any.html
Actual
FAIL
Expected
FAIL
Unexpected
no
Duration
3402 ms
Harness
OK
Counts
Reason
Run
https://kitesurf.rendering.cfdata.org/?url=http%3A%2F%2Fwpt.live%2Fstreams%2Fwritable-streams%2Faborting.any.html ↗
Upstream
view on github.com/web-platform-tests/wpt ↗

Subtests

statussubtestmessage
FAILAborting a WritableStream before it starts should cause the writer's unsettled ready promise to rejectassert_unreached: write() should not be called Reached unreachable code
PASSAborting a WritableStream should cause the writer's fulfilled ready promise to reset to a rejected one
PASSabort() on a released writer rejects
PASSAborting a WritableStream immediately prevents future writes
PASSAborting a WritableStream prevents further writes after any that are in progress
PASSFulfillment value of writer.abort() call must be undefined even if the underlying sink returns a non-undefined value
PASSWritableStream if sink's abort throws, the promise returned by writer.abort() rejects
FAILWritableStream if sink's abort throws, the promise returned by multiple writer.abort()s is the same and rejectsassert_equals: the promises must be the same expected object "[object Promise]" but got object "[object Promise]"
PASSWritableStream if sink's abort throws, the promise returned by ws.abort() rejects
PASSWritableStream if sink's abort throws, for an abort performed during a write, the promise returned by ws.abort() rejects
PASSAborting a WritableStream passes through the given reason
PASSAborting a WritableStream puts it in an errored state with the error passed to abort()
FAILAborting a WritableStream causes any outstanding write() promises to be rejected with the reason suppliedassert_unreached: Should have rejected: writing should reject with error1 Reached unreachable code
PASSClosing but then immediately aborting a WritableStream causes the stream to error
PASSClosing a WritableStream and aborting it while it closes causes the stream to ignore the abort attempt
PASSAborting a WritableStream after it is closed is a no-op
PASSWritableStream should NOT call underlying sink's close if no abort is supplied (historical)
PASSreturning a thenable from abort() should work
PASS.closed should not resolve before fulfilled write()
PASS.closed should not resolve before rejected write(); write() error should not overwrite abort() error
PASSwrites should be satisfied in order when aborting
PASSwrites should be satisfied in order after rejected write when aborting
PASSclose() should reject with abort reason why abort() is first error
PASSunderlying abort() should not be called until underlying write() completes
PASSunderlying abort() should not be called if underlying close() has started
PASSif underlying close() has started and then rejects, the abort() and close() promises should reject with the underlying close rejection reason
PASSan abort() that happens during a write() should trigger the underlying abort() even with a close() queued
PASSif a writer is created for a stream with a pending abort, its ready should be rejected with the abort error
PASSwriter close() promise should resolve before abort() promise
PASSwriter.ready should reject on controller error without waiting for underlying write
FAILwriter.abort() while there is an in-flight write, and then finish the write with rejectionpromise_rejects_js: writer.closed must be rejected with an error indicating release function "function() { throw e; }" threw object "error1: error1" ("error1") expected instance of function "function …
FAILwriter.abort(), controller.error() while there is an in-flight write, and then finish the writepromise_rejects_js: writer.closed must be rejected with an error indicating release function "function() { throw e; }" threw object "error1: error1" ("error1") expected instance of function "function …
FAILwriter.abort(), controller.error() while there is an in-flight close, and then finish the closeassert_unreached: Should have rejected: writer.closed must be rejected with an error indicating release Reached unreachable code
FAILcontroller.error(), writer.abort() while there is an in-flight write, and then finish the writepromise_rejects_js: writer.closed must be rejected with an error indicating release function "function() { throw e; }" threw object "error2: error2" ("error2") expected instance of function "function …
FAILcontroller.error(), writer.abort() while there is an in-flight close, and then finish the closeassert_unreached: Should have rejected: writer.closed must be rejected with an error indicating release Reached unreachable code
PASSreleaseLock() while aborting should reject the original closed promise
PASSreleaseLock() during delayed async abort() should reject the writer.closed promise
PASSsink abort() should not be called until sink start() is done
PASSif start attempts to error the controller after abort() has been called, then it should lose
PASSstream abort() promise should still resolve if sink start() rejects
PASSwriter abort() during sink start() should replace the writer.ready promise synchronously
PASSpromises returned from other writer methods should be rejected when writer abort() happens during sink start()
PASSabort() should succeed despite rejection from write
PASSabort() should be rejected with the rejection returned from close()
PASSa rejecting sink.write() should not prevent sink.abort() from being called
PASSwhen start errors after stream abort(), underlying sink abort() should be called anyway
FAILwhen calling abort() twice on the same stream, both should give the same promise that fulfills with undefinedassert_equals: the promises must be the same expected object "[object Promise]" but got object "[object Promise]"
PASSwhen calling abort() twice on the same stream, but sequentially so so there's no pending abort the second time, both should fulfill with undefined
PASScalling abort() on an errored stream should fulfill with undefined
PASSsink abort() should not be called if stream was erroring due to controller.error() before abort() was called
FAILsink abort() should not be called if stream was erroring due to bad strategy before abort() was calledpromise_rejects_js: second write() should reject function "function() { throw e; }" threw object "TypeError: The value cannot be converted because it is not an integer." ("TypeError") expected instanc…
PASSabort with no arguments should set the stored error to undefined
PASSabort with an undefined argument should set the stored error to undefined
PASSabort with a string argument should set the stored error to that argument
PASSabort on a locked stream should reject
PASSWritableStreamDefaultController.signal
FAILthe abort signal is signalled synchronously - writeassert_true: signal.reason is a DOMException expected true got false
PASSthe abort signal is signalled synchronously - close
PASSthe abort signal is not signalled on error
PASSthe abort signal is not signalled on write failure
PASSthe abort signal is not signalled on close failure
PASSrecursive abort() call from abort() aborting signal (not started)
PASSrecursive abort() call from abort() aborting signal
PASSrecursive close() call from abort() aborting signal (not started)
PASSrecursive close() call from abort() aborting signal

bundle built 2026-07-16T07:16:48.063Z