Closed Bug 1900760 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 46630 - Move SW static routing API tests out of tentative

Categories

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

Product:
Core
Component:
DOM: Service Workers
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
128 Branch
Tracking Flags:
Tracking Status
firefox128 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Yoshisato Yanagisawa <yyanagisawa@chromium.org> wrote:

Move SW static routing API tests out of tentative

Since the ServiceWorker static routing API has already included in the
specification, let me move them out from tentative.

Change-Id: I8d16647f990ee4daad9f3797a18f3ec1040ad2f8
Bug: 327026291
Reviewed-on: https://chromium-review.googlesource.com/5595077
WPT-Export-Revision: 023be2302db0909dd26a2177e3a91f6047e8bb5b

Component: web-platform-tests → DOM: Service Workers
Product: Testing → Core

CI Results

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

Total 11 tests and 14 subtests

Status Summary

Firefox

OK : 11
FAIL: 67

Chrome

OK : 11
PASS: 51
FAIL: 16

Safari

OK : 11
FAIL: 67

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /service-workers/service-worker/static-router-fetch-event.https.html [wpt.fyi]
    • Main resource matched the rule with fetch-event source: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched the rule fetch-event source: FAIL (Chrome: PASS, Safari: FAIL)
  • /service-workers/service-worker/static-router-invalid-rules.https.html [wpt.fyi]
    • addRoutes should raise for invalid request method.: FAIL (Chrome: PASS, Safari: FAIL)
    • addRoutes should raise if or condition exceeds the depth limit: FAIL (Chrome: PASS, Safari: FAIL)
    • addRoutes should raise if not condition exceeds the depth limit: FAIL (Chrome: PASS, Safari: FAIL)
    • addRoutes should raise if the number of router rules exceeds the length limit: FAIL (Chrome: PASS, Safari: FAIL)
    • addRoutes should raise if the conditon does not exist in the rule: FAIL (Chrome: PASS, Safari: FAIL)
    • addRoutes should raise if the source does not exiswt in the rule: FAIL (Chrome: PASS, Safari: FAIL)
  • /service-workers/service-worker/static-router-main-resource.https.html [wpt.fyi]
    • Main resource load matched with the condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Main resource load matched with the ignore case condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Main resource load matched without the ignore case condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Main resource load not matched with the condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Main resource load matched with the cache source: FAIL (Chrome: PASS, Safari: FAIL)
    • Main resource fallback to the network when there is no cache entry: FAIL (Chrome: PASS, Safari: FAIL)
    • Main resource load matched with the cache source, with specifying the cache name: FAIL (Chrome: PASS, Safari: FAIL)
    • Main resource load should not match the condition with not: FAIL (Chrome: PASS, Safari: FAIL)
    • Main resource load should match the condition without not: FAIL (Chrome: FAIL, Safari: FAIL)
  • /service-workers/service-worker/static-router-multiple-router-registrations.https.html [wpt.fyi]
    • Main reosurce load matched with the service worker having multiple rules: FAIL (Chrome: PASS, Safari: FAIL)
    • Resource load matched with the rule registered in the imported service worker: FAIL (Chrome: PASS, Safari: FAIL)
  • /service-workers/service-worker/static-router-mutiple-conditions.https.html [wpt.fyi]
    • Multiple conditions work with and operation: FAIL (Chrome: PASS, Safari: FAIL)
    • Multiple conditions including requestDestination work with and operation: FAIL (Chrome: PASS, Safari: FAIL)
  • /service-workers/service-worker/static-router-no-fetch-handler.https.html [wpt.fyi]
    • The router rule is evaluated without fetch handlers in service worker: FAIL (Chrome: PASS, Safari: FAIL)
    • addRoutes should raise if the fetch-event source is used without onfetch: FAIL (Chrome: PASS, Safari: FAIL)
  • /service-workers/service-worker/static-router-race-network-and-fetch-handler.https.html [wpt.fyi]
    • 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: PASS, 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: PASS, 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: PASS, 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: PASS, Safari: FAIL)
    • Subresource load matched the rule with race-network-and-fetch-handler source, and the server reseponse with 204 response is faster than the fetch handler: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched the rule with race-network-and-fetch-handler source, and the server reseponse is faster than the fetch handler, but not found: FAIL (Chrome: PASS, Safari: FAIL)
  • /service-workers/service-worker/static-router-request-destination.https.html [wpt.fyi]
    • Subreosurce load matched with the requestMethod script condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subreosurce load not matched with the requestMethod script condition: FAIL (Chrome: PASS, Safari: FAIL)
  • /service-workers/service-worker/static-router-request-method.https.html [wpt.fyi]
    • Subresource load matched with the requestMethod GET condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with the requestMethod POST condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with the requestMethod PUT condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with the requestMethod DELETE condition: FAIL (Chrome: PASS, Safari: FAIL)
  • /service-workers/service-worker/static-router-subresource.https.html [wpt.fyi]
    • Subresource load not matched with URLPattern condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with URLPattern condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource cross origin load matched with URLPattern condition via constructed object: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with ignoreCase URLPattern condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched without ignoreCase URLPattern condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with URLPattern condition via URLPatternCompatible: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource cross origin load not matched with URLPattern condition via URLPatternCompatible: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with URLPattern condition via string: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource cross origin load not matched with URLPattern condition via string: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with RequestMode condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with the nested or condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with the next or condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load not matched with or condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with the cache source rule: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load did not match with the cache and fallback to the network: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load matched with the cache source, with specifying the cache name: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load should not match with the not condition: FAIL (Chrome: PASS, Safari: FAIL)
    • Subresource load should match with a file other than not: FAIL (Chrome: FAIL, Safari: FAIL)
  • /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: FAIL, Safari: FAIL)
    • Main resource load matched with the condition and resource timing: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource load not matched with the condition and resource timing: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource load matched with the cache source and resource timing: FAIL (Chrome: FAIL, Safari: FAIL)
    • Main resource fallback to the network when there is no cache entry and resource timing: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load matched the rule fetch-event source: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load not matched with URLPattern condition: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load matched with URLPattern condition: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load matched with the cache source rule: FAIL (Chrome: FAIL, Safari: FAIL)
    • Subresource load did not match with the cache and fallback to the network: FAIL (Chrome: FAIL, 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: FAIL, 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: FAIL, 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: FAIL, 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: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/470989069673 [wpt PR 46630] - Move SW static routing API tests out of tentative, a=testonly https://hg.mozilla.org/integration/autoland/rev/98cabb8adeef [wpt PR 46630] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/470989069673
https://hg.mozilla.org/mozilla-central/rev/98cabb8adeef

Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox128: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in before you can comment on or make changes to this bug.