Open Bug 1832965 Opened 3 years ago Updated 1 year ago

New wpt failures in /dom/abort/ [abort-signal-any.any.worker.html, abort-signal-any.any.html]

Categories

(Core :: DOM: Core & HTML, defect)

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

Tracking

()

People

(Reporter: wpt-sync, Unassigned)

References

Details

(Whiteboard: [wpt])

Syncing wpt PR 39785 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

  • /dom/abort/abort-signal-any.any.worker.html [wpt.fyi]
    • AbortSignal.any() works with an empty array of signals: FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() follows a single signal (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() follows multiple signals (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() returns an aborted signal if passed an aborted signal (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() can be passed the same signal more than once (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() uses the first instance of a duplicate signal (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() signals are composable (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() works with signals returned by AbortSignal.timeout() (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() works with intermediate signals (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • Abort events for AbortSignal.any() signals fire in the right order (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
  • /dom/abort/abort-signal-any.any.html [wpt.fyi]
    • AbortSignal.any() works with an empty array of signals: FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() follows a single signal (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() follows multiple signals (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() returns an aborted signal if passed an aborted signal (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() can be passed the same signal more than once (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() uses the first instance of a duplicate signal (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() signals are composable (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() works with signals returned by AbortSignal.timeout() (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • AbortSignal.any() works with intermediate signals (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)
    • Abort events for AbortSignal.any() signals fire in the right order (using AbortController): FAIL (Chrome: PASS, Safari: FAIL)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1830775 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.

Severity: -- → S4
You need to log in before you can comment on or make changes to this bug.