[Webkit-unassigned] [Bug 172510] New: [macOS Sierra WK2] Layout Test imported/w3c/web-platform-tests/fetch/api/request/request-cache-reload.html is flaky

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=172510

            Bug ID: 172510
           Summary: [macOS Sierra WK2] Layout Test
                    imported/w3c/web-platform-tests/fetch/api/request/requ
                    est-cache-reload.html is flaky
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jlewis3 at apple.com

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

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170523/f0913497/attachment-0001.html>