[wpt-sync] Sync PR 46182 - Add WPTs for ServiceWorker Static Routing API Resource Timing
Categories
(Core :: DOM: Service Workers, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox128 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 46182 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/46182
Details from upstream follow.
Keita Suzuki <suzukikeita@chromium.org> wrote:
Add WPTs for ServiceWorker Static Routing API Resource Timing
This CL adds WPTs for Service Worker Static Routing API Resource Timing.
It conducts a set of tests to determine if the resource timing is
correctly working on each source type, and on main and sub-resources.explainer: XXX
Bug: 41496865
Change-Id: Ide7d352d4824b9491645964febb6522ffe71aafbReviewed-on: https://chromium-review.googlesource.com/5521193
WPT-Export-Revision: dcad81d49f313f716153049e0e4ece34b904d987
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 1•2 years ago
|
||
| Assignee | ||
Comment 2•2 years ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 14 subtests
Status Summary
Firefox
OK : 1
FAIL : 14
Chrome
TIMEOUT: 2
NOTRUN : 13
Safari
OK : 1
FAIL : 14
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
- /service-workers/service-worker/tentative/static-router/static-router-resource-timing.https.html [wpt.fyi]
- Main resource matched the rule with fetch-event source:
FAIL(Chrome:TIMEOUT, Safari:FAIL) - Main resource load matched with the condition and resource timing:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Main resource load not matched with the condition and resource timing:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Main resource load matched with the cache source and resource timing:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Main resource fallback to the network when there is no cache entry and resource timing:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Subresource load matched the rule fetch-event source:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Subresource load not matched with URLPattern condition:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Subresource load matched with URLPattern condition:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Subresource load matched with the cache source rule:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Subresource load did not match with the cache and fallback to the network:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Main resource load matched the rule with race-network-and-fetch-handler source, and the fetch handler response is faster than the server response:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Main resource load matched the rule with race-network-and-fetch-handler source, and the server reseponse is faster than the fetch handler:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Subresource load matched the rule with race-network-and-fetch-handler source, and the fetch handler response is faster than the server response:
FAIL(Chrome:NOTRUN, Safari:FAIL) - Subresource load matched the rule with race-network-and-fetch-handler source, and the server reseponse is faster than the fetch handler:
FAIL(Chrome:NOTRUN, Safari:FAIL)
- Main resource matched the rule with fetch-event source:
https://hg.mozilla.org/mozilla-central/rev/3c9f8c44f543
https://hg.mozilla.org/mozilla-central/rev/e615bd2f2a61
Description
•