Closed Bug 1773516 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 34362 - Scheduling APIs: Don't clear algorithms after priority change

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox103 fixed)

RESOLVED FIXED
103 Branch
Tracking Status
firefox103 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 34362 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/34362
Details from upstream follow.

Scott Haseley <shaseley@chromium.org> wrote:

Scheduling APIs: Don't clear algorithms after priority change

We're clearing priority change algorithms after they run, but priority
can change repeatedly. We got it right in the spec, but probably copied
the AbortSignal behavior over in the implementation. This CL fixes that
and adds WPT tests.

Bug: None
Change-Id: I6eca3c92a14ad9d6ad73afc8a57adca871d3faa0
Reviewed-on: https://chromium-review.googlesource.com/3697179
WPT-Export-Revision: 1e4865813e5c3eef400dcdc898a30773d325bb4c

CI Results

Ran 11 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 4 tests and 2 subtests

Status Summary

Firefox

OK : 4
PASS: 8

Chrome

OK : 4
FAIL: 8

Safari

OK : 4
FAIL: 8

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b07ad91d480c [wpt PR 34362] - Scheduling APIs: Don't clear algorithms after priority change, a=testonly
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a65119eeb48d [wpt PR 34362] - Scheduling APIs: Don't clear algorithms after priority change, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 103 Branch
You need to log in before you can comment on or make changes to this bug.