kitesurf · WPT

FAIL
expected FAIL · 707 ms
▶ run in kitesurf
Test
/dom/abort/abort-signal-any.any.html
Actual
FAIL
Expected
FAIL
Unexpected
no
Duration
707 ms
Harness
OK
Counts
Reason
Run
https://kitesurf.rendering.cfdata.org/?url=http%3A%2F%2Fwpt.live%2Fdom%2Fabort%2Fabort-signal-any.any.html ↗
Upstream
view on github.com/web-platform-tests/wpt ↗

Subtests

statussubtestmessage
PASSAbortSignal.any() works with an empty array of signals
PASSAbortSignal.any() follows a single signal (using LazyAbortController)
PASSAbortSignal.any() follows multiple signals (using LazyAbortController)
PASSAbortSignal.any() returns an aborted signal if passed an aborted signal (using LazyAbortController)
PASSAbortSignal.any() can be passed the same signal more than once (using LazyAbortController)
PASSAbortSignal.any() uses the first instance of a duplicate signal (using LazyAbortController)
PASSAbortSignal.any() signals are composable (using LazyAbortController)
PASSAbortSignal.any() works with signals returned by AbortSignal.timeout() (using LazyAbortController)
PASSAbortSignal.any() works with intermediate signals (using LazyAbortController)
FAILAbort events for AbortSignal.any() signals fire in the right order (using LazyAbortController)assert_equals: expected "01234" but got "41230"
PASSDependent signals for AbortSignal.any() are marked aborted before abort events fire (using LazyAbortController)
PASSDependent signals for AbortSignal.any() are aborted correctly for reentrant aborts (using LazyAbortController)
PASSDependent signals for AbortSignal.any() should use the same DOMException instance from the already aborted source signal (using LazyAbortController)
PASSDependent signals for AbortSignal.any() should use the same DOMException instance from the source signal being aborted later (using LazyAbortController)

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