1735723 - [wpt-sync] Sync PR 31229 - Test interactions of Fetch, ResourceTiming and ServiceWorkers

Status: RESOLVED FIXED

(Core :: DOM: Service Workers, task, P4)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

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

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

Noam Rosenthal <[e-mail]> wrote:

Test interactions of Fetch, ResourceTiming and ServiceWorkers

• Worker induced delays should be reflected in ResourceTiming entry
• Redirects & connection info should not be forwarded to the client
• Worker-induced delays should occur before responseStart
• requestStart should occur after fetchStart

Addresses https://github.com/whatwg/fetch/issues/1208
See https://github.com/web-platform-tests/wpt/issues/28658

Comment 1

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=b52af9a2389f922cd7238472d571ad9a5a1cc305

Comment 2

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

CI Results

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

Total 1 tests and 5 subtests

Status Summary

Firefox

OK : 1
PASS: 2
FAIL: 3

Chrome

OK : 1
PASS: 4
FAIL: 1

Safari

OK : 1
PASS: 2
FAIL: 3

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

/service-workers/service-worker/resource-timing-fetch-variants.https.html
Redirects done from within a service-worker should not be exposed to client ResourceTiming: FAIL

New Tests That Don't Pass

/service-workers/service-worker/resource-timing-fetch-variants.https.html
Redirects done from within a service-worker should not be exposed to client ResourceTiming: FAIL (Chrome: PASS, Safari: PASS)
Delay from within service-worker (after internal fetching) should be accessible through responseStart: FAIL (Chrome: PASS, Safari: FAIL)
Delay from within service-worker (before internal fetching) should be measured before responseStart in the client ResourceTiming entry: FAIL (Chrome: PASS, Safari: FAIL)

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/dd27a26b614d
[wpt PR 31229] - Test interactions of Fetch, ResourceTiming and ServiceWorkers, a=testonly
https://hg.mozilla.org/integration/autoland/rev/7cc2b77e7905
[wpt PR 31229] - Update wpt metadata, a=testonly

Comment 4

[Atila Butkovits]

https://hg.mozilla.org/mozilla-central/rev/dd27a26b614d
https://hg.mozilla.org/mozilla-central/rev/7cc2b77e7905