RESOLVED WORKSFORME 217412
REGRESSION(iOS 14): http/wpt/cache-storage/cache-quota.any.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=217412
Summary REGRESSION(iOS 14): http/wpt/cache-storage/cache-quota.any.html is a flaky fa...
Hector Lopez
Reported 2020-10-06 15:51:50 PDT
http/wpt/cache-storage/cache-quota.any.html Test is a flaky failure according to history on iOS. First occurrence of failure coincides with the start of testing on iOS 14. Test is not a flaky failure on iOS 13. Of note also is that there is a test expectation for [this test as listed here: LayoutTests/platform/ios-simulator-wk2/TestExpectations:48:http/wpt/cache-storage/cache-quota.any.html [ Slow ] History: https://results.webkit.org/?suite=layout-tests&test=http%2Fwpt%2Fcache-storage%2Fcache-quota.any.html&platform=ios Diff: --- /Volumes/Data/slave/ios-simulator-14-release-tests-wk2/build/layout-test-results/http/wpt/cache-storage/cache-quota.any-expected.txt +++ /Volumes/Data/slave/ios-simulator-14-release-tests-wk2/build/layout-test-results/http/wpt/cache-storage/cache-quota.any-actual.txt @@ -1,9 +1,10 @@ CONSOLE MESSAGE: Cache API operation failed: Quota exceeded -CONSOLE MESSAGE: Cache API operation failed: Quota exceeded + +Harness Error (TIMEOUT), message = null PASS Testing synthetic response body size padding PASS Testing non opaque response body size padding PASS Testing opaque response body size padding PASS Hitting cache quota for non opaque responses -PASS Hitting cache quota for padded responses +TIMEOUT Hitting cache quota for padded responses Test timed out
Attachments
Radar WebKit Bug Importer
Comment 1 2020-10-06 15:52:05 PDT
Hector Lopez
Comment 2 2020-10-06 15:55:32 PDT
Test expectation while investigated: https://trac.webkit.org/changeset/268081/webkit
Karl Rackler
Comment 3 2020-10-08 09:55:40 PDT
Move test expectations from ios-wk2 to ios-simulator-wk2 https://trac.webkit.org/changeset/268186/webkit
Ben Schwartz
Comment 4 2024-03-22 22:40:51 PDT
This test hasn't failed since March 18, 2023 (iOS 16). Is it safe to say this is resolved?
Note You need to log in before you can comment on or make changes to this bug.