Closed Bug 1771180 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 34203 - [BroadcastChannel] Use long timeout for opaque-origin tests

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
102 Branch
Tracking Status
firefox102 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Andrew Williams <awillia@google.com> wrote:

[BroadcastChannel] Use long timeout for opaque-origin tests

I haven't been able to confirm that this addresses the flakiness
with these tests, but the data URL worker tests do a similar amount
of work to the cross-partition tests which do seem to need the long
timeout.

Bug: 1322297
Change-Id: I585b24fd884fd135edc163cad77ea8ee56f11e9d
Reviewed-on: https://chromium-review.googlesource.com/3668704
WPT-Export-Revision: 0321309282565c7d226f6fb30e80215e3d148d38

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

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

Total 1 tests and 4 subtests

Status Summary

Firefox

OK : 1
PASS: 4

Chrome

OK : 1
PASS: 2
FAIL: 2

Safari

OK : 1
PASS: 3
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0b17ae00819b
[wpt PR 34203] - [BroadcastChannel] Use long timeout for opaque-origin tests, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
You need to log in before you can comment on or make changes to this bug.