Closed Bug 1800145 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 36915 - Address flakiness issue in permissions/permissions-cg.https.html

Categories

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

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox108 fixed)

Status:
RESOLVED FIXED
Milestone:
108 Branch
Tracking Flags:
Tracking Status
firefox108 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Chris Dumez <cdumez@apple.com> wrote:

Address flakiness issue in permissions/permissions-cg.https.html

Make sure the PermissionStatus object gets constructed and its change event listener gets registered BEFORE we update the permission state. Previously, the order wasn't guaranteed and this would lead to flakiness because the change would get fired before the event listener got added.

Also trigger garbage collection explicitly to make it more likely to trigger GC bugs, given that this is what the test intends to cover.

This is a merge from https://github.com/WebKit/WebKit/pull/6358.

CI Results

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

Total 1 tests and 1 subtests

Status Summary

Firefox

TIMEOUT: 1
ERROR : 1

Chrome

ERROR : 1

Safari

TIMEOUT: 1
ERROR : 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8b37a3482329
[wpt PR 36915] - Address flakiness issue in permissions/permissions-cg.https.html, a=testonly
https://hg.mozilla.org/integration/autoland/rev/2c8a33fda88d
[wpt PR 36915] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/8b37a3482329
https://hg.mozilla.org/mozilla-central/rev/2c8a33fda88d

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox108: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.