RESOLVED DUPLICATE of bug 237160 237158
REGRESSION: [ iOS ] 3 service-workers tests failing constantly 
https://bugs.webkit.org/show_bug.cgi?id=237158
Summary REGRESSION: [ iOS ] 3 service-workers tests failing constantly
Truitt Savell
Reported 2022-02-24 14:29:15 PST
imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https.html imported/w3c/web-platform-tests/service-workers/service-worker/partitioned-service-worker-getRegistrations.tentative.https.html imported/w3c/web-platform-tests/service-workers/service-worker/partitioned-service-worker.tentative.https.html These three tests began failing constantly on iOS and flakily on MacOS around 247674@main imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https.html seems to be a progression with a passing message, the other two now have failing messages History: https://results.webkit.org/?suite=layout-tests&suite=layout-tests&suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fservice-workers%2Fservice-worker%2Ffetch-request-no-freshness-headers.https.html&test=imported%2Fw3c%2Fweb-platform-tests%2Fservice-workers%2Fservice-worker%2Fpartitioned-service-worker-getRegistrations.tentative.https.html&test=imported%2Fw3c%2Fweb-platform-tests%2Fservice-workers%2Fservice-worker%2Fpartitioned-service-worker.tentative.https.html Diff: --- /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https-expected.txt +++ /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https-actual.txt @@ -1,3 +1,3 @@ -FAIL The headers of FetchEvent shouldn't contain freshness headers. assert_false: if-none-match header must not be set in the FetchEvent's request. (url = https://localhost:9443/service-workers/service-worker/resources/fetch-request-no-freshness-headers-script.py) expected false got true +PASS The headers of FetchEvent shouldn't contain freshness headers. --- /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/partitioned-service-worker-getRegistrations.tentative.https-expected.txt +++ /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/partitioned-service-worker-getRegistrations.tentative.https-actual.txt @@ -1,4 +1,4 @@ This test loads a SW in a first-party context and gets the SW's (randomly) generated ID. It does the same thing for the SW but in a third-party context and then confirms that the IDs are different. -PASS ServiceWorker's getRegistration() is partitioned +FAIL ServiceWorker's getRegistration() is partitioned assert_true: 1p SW didn't shutdown expected true got false --- /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/partitioned-service-worker.tentative.https-expected.txt +++ /Volumes/Data/worker/ios-simulator-15-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/partitioned-service-worker.tentative.https-actual.txt @@ -1,6 +1,6 @@ The 3p iframe's postMessage: -3p iframe's has_pending: false source: From3pFrame. 1p iframe's has_pending: true source: From1pFrame +3p iframe's has_pending: false source: From3pFrame. -PASS Services workers under different top-level sites are partitioned. +FAIL Services workers under different top-level sites are partitioned. assert_equals: The 1p frames were serviced by different service workers. expected 0.47079193065486125 but got 0.8715043792549053
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2022-02-24 14:29:33 PST
<rdar://problem/89439565>
Brent Fulgham
Comment 2 2022-06-23 15:33:57 PDT
*** This bug has been marked as a duplicate of bug 237160 ***
Note You need to log in before you can comment on or make changes to this bug.