Closed Bug 1622434 Opened 8 months ago Closed 8 months ago

[wpt-sync] Sync PR 22247 - Using WPT metadata to mark fetch.https.any.js test as slow.

Categories

(Core :: DOM: Networking, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla76
Tracking Status
firefox76 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Lukasz Anforowicz <lukasza@chromium.org> wrote:

Using WPT metadata to mark fetch.https.any.js test as slow.

This CL annotates cross-origin-resource-policy/fetch.https.any.js with:
// META: timeout=long
and removes [ Timeout ] expectations that this test has accumulated in
blink/web_tests/TestExpectations over multiple sheriffing duties.

Bug: 626703
Fixed: 1012599
Change-Id: Ia26c9200bc4182fb7fe51c98fd256079175c0801

Reviewed-on: https://chromium-review.googlesource.com/2103074
WPT-Export-Revision: 0bfc74bd63f1e6c27665618759ccd41dcc69fd1c

Component: web-platform-tests → DOM: Networking
Product: Testing → Core

CI Results

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

Total 4 tests and 9 subtests

Status Summary

Firefox

OK : 4
PASS: 36

Chrome

OK : 4
PASS: 36

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2d5575ebd604
[wpt PR 22247] - Using WPT metadata to mark fetch.https.any.js test as slow., a=testonly
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in before you can comment on or make changes to this bug.