Closed Bug 1667364 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 25787 - [COOP] access reporting: Use infinite timeout for receive.

Categories

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

task

Tracking

()

RESOLVED FIXED
83 Branch
Tracking Status
firefox83 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

b'arthursonzogni <arthursonzogni@chromium.org>' wrote:

[COOP] access reporting: Use infinite timeout for receive.

Some browsers do not implement COOP reporting. As a result, no reports
are received after a 2.5s timeout.

Waiting 2.5s many time can reach the global timeout. Sometime, this
flakes in between FAIL and TIMEOUT.

This patch makes the timeout to be infinite by default to get consistent
failure.

Bug:1090273
Change-Id: I081b9c8e944fc50b391753ce0948392b88d3fd0e

Reviewed-on: https://chromium-review.googlesource.com/2428976
WPT-Export-Revision: e0e852b424d3fb4fef0a8aede79df0a2b671a190

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
PR 25787 applied with additional changes from upstream: 2fef4d6f7ce1c5e0af3ed8421b2bc30eddb934f2, dbb8a3ff33b3cca0899018e7dee3989842017976

CI Results

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

Total 31 tests and 2 subtests

Status Summary

Safari

OK : 6
PASS : 6
FAIL : 18
TIMEOUT: 50
NOTRUN : 69

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a615464db6af [wpt PR 25787] - [COOP] access reporting: Use infinite timeout for receive., a=testonly https://hg.mozilla.org/integration/autoland/rev/67b0d4533343 [wpt PR 25787] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in before you can comment on or make changes to this bug.