Summary: | REGRESSION: (r262432): [ iOS wk2 ] imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https.html is flaky failing. | ||
---|---|---|---|
Product: | WebKit | Reporter: | Jason Lawrence <Lawrence.j> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | webkit-bot-watchers-bugzilla, webkit-bug-importer, youennf |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | iPhone / iPad | ||
OS: | iOS 13 | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=212464 |
Description
Jason Lawrence
2020-06-03 08:38:10 PDT
I can reproduce this issue with r262432, but I cannot reproduce it with r262431. Command: run-webkit-tests --ios-simulator --iterations 99 --exit-after-n-failures 3 imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https.html r262432 results: [1/99] imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https.html failed unexpectedly (text diff) [2/99] imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https.html failed unexpectedly (text diff) [3/99] imported/w3c/web-platform-tests/service-workers/service-worker/fetch-request-no-freshness-headers.https.html failed unexpectedly (text diff) Exiting early after 3 failures. 3 tests run. 0 tests ran as expected, 3 didn't (96 didn't run): r262431 results: All 99 tests ran as expected. I have marked this test as flaky failing while this issue is investigated. https://trac.webkit.org/changeset/262489/webkit https://trac.webkit.org/changeset/262489/webkit is most probably ensuring that the service worker is run in the same process as the page, thus potentially reusing the memory cache. It seems strange though that this is iOS sim only. Or maybe this is due to timing, and the reuse of the existing process makes the test run a bit faster. I do not think we are breaking behavior. I have removed the expectations because the test no longer appears to be failing: https://trac.webkit.org/changeset/263507/webkit |