Closed Bug 1715792 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 29330 - [ResourceTiming] Refactor connection-reuse tests

Categories

(Core :: Performance, task, P4)

task

Tracking

()

RESOLVED FIXED
91 Branch
Tracking Status
firefox91 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

b'Tom McKee <tommckee@chromium.org>' wrote:

[ResourceTiming] Refactor connection-reuse tests

This CL migrates the connection reuse WPTs to the new style. See
wpt/resource-timing/CodingConventions.md for details.

These tests exist to verify that the Resource Timing API yields correct
PerformanceResourceTiming values when the underlying TCP connection is
reused across multiple subresources.

Bug: 1171767
Change-Id: I5acdb6bf8a5e71bb34c7d2236cdb9d0209d3d04d
GithubIssue: https://github.com/w3c/resource-timing/issues/254
Reviewed-on: https://chromium-review.googlesource.com/2950880
WPT-Export-Revision: 3a26c21e4c0967f76edef74ec52d2bb8a2534e61

Component: web-platform-tests → Performance
Product: Testing → Core

CI Results

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

Total 4 tests and 9 subtests

Status Summary

Firefox

OK : 4
PASS : 19
FAIL : 1

Chrome

OK : 4
PASS : 20

Safari

OK : 3
PASS : 5
FAIL : 12
TIMEOUT: 2
NOTRUN : 2

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/resource-timing/iframe-failed-commit.html
Test iframe from non-existent host: FAIL (Chrome: PASS, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1b909873a7e8
[wpt PR 29330] - [ResourceTiming] Refactor connection-reuse tests, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.