Bug 172510

Summary: [macOS Sierra WK2] Layout Test imported/w3c/web-platform-tests/fetch/api/request/request-cache-reload.html is flaky
Product: WebKit Reporter: Matt Lewis <jlewis3>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: cdumez, youennf
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Matt Lewis
Reported 2017-05-23 11:03:04 PDT
The test imported/w3c/web-platform-tests/fetch/api/request/request-cache-reload.html is a flaky failure. The test has been flaky on Sierra Leaks for a while however is now started failing intermittently on Sierra Debug and Release since 5/19 The test had expectations changed in: https://trac.webkit.org/changeset/213882/webkit https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2Ffetch%2Fapi%2Frequest%2Frequest-cache-reload.html https://build.webkit.org/builders/Apple%20Sierra%20Release%20WK2%20(Tests)/builds/1704 https://build.webkit.org/results/Apple%20Sierra%20Release%20WK2%20(Tests)/r217280%20(1704)/results.html Diff: --- /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/fetch/api/request/request-cache-reload-expected.txt +++ /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/fetch/api/request/request-cache-reload-actual.txt @@ -5,8 +5,8 @@ PASS RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and fresh response PASS RequestCache "reload" mode does store the response in the cache with Etag and stale response PASS RequestCache "reload" mode does store the response in the cache with Last-Modified and stale response -PASS RequestCache "reload" mode does store the response in the cache with Etag and fresh response -PASS RequestCache "reload" mode does store the response in the cache with Last-Modified and fresh response +FAIL RequestCache "reload" mode does store the response in the cache with Etag and fresh response assert_equals: expected 1 but got 2 +FAIL RequestCache "reload" mode does store the response in the cache with Last-Modified and fresh response assert_equals: expected 1 but got 2 PASS RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Etag and stale response PASS RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and stale response PASS RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Etag and fresh response
Attachments
Note You need to log in before you can comment on or make changes to this bug.