Closed Bug 1900936 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 46641 - Add internal WPT for SW static routing API

Categories

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

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

Tracking

()

Status:
RESOLVED FIXED
Milestone:
129 Branch
Tracking Flags:
Tracking Status
firefox129 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Keita Suzuki <suzukikeita@chromium.org> wrote:

Add internal WPT for SW static routing API

This CL adds internal WPT for SW static routing API to test the behavior
when the router evaluator could not parse the regular expression
provided by developers. Since this is due to the regex framework
re2, chrome raises a PromiseError when encountering this situation.

Bug: 41492364
Change-Id: I13573d5b7060ab55a51727a66a17acfd5ec34d0c
Reviewed-on: https://chromium-review.googlesource.com/5595296
WPT-Export-Revision: 305cfdb5410b27904884d02bfac60e8845f4218b

PR 46641 applied with additional changes from upstream: 6e5bea725e29fec0a05db94ceb5f61b25f4f3723
Component: web-platform-tests → DOM: Service Workers
Product: Testing → Core

CI Results

Ran 0 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

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/6310c910d53e [wpt PR 46641] - Add internal WPT for SW static routing API, a=testonly

https://hg.mozilla.org/mozilla-central/rev/6310c910d53e

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox129: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
You need to log in before you can comment on or make changes to this bug.