[Webkit-unassigned] [Bug 208937] New: [WPE] Several fetch api tests are flaky after r256986

[bugzilla-daemon at webkit.org]

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

            Bug ID: 208937
           Summary: [WPE] Several fetch api tests are flaky after r256986
           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: dpino at igalia.com

The following tests became flaky after r256986:

   imported/w3c/web-platform-tests/fetch/api/basic/conditional-get.html [ Failure Pass ]
   imported/w3c/web-platform-tests/fetch/api/request/request-cache-default.html [ Failure Pass ]
   imported/w3c/web-platform-tests/fetch/api/request/request-cache-force-cache.html [ Failure Pass ]
   imported/w3c/web-platform-tests/fetch/api/request/request-cache-reload.html [ Failure Pass ]

wk-testhunter reports the tests became flaky at:

r256950                       NOERROR
[r256951-r256986]             UNKNOWN
r256987                       TEXT PASS (Expected: PASS)

It's hard to determine which revision caused the regression within that range, since there are many revisions that don't have a corresponding git commit.

Diff:

--- /home/dpino/workspace/webkit-wpe/layout-test-results/imported/w3c/web-platform-tests/fetch/api/request/request-cache-reload-expected.txt
+++ /home/dpino/workspace/webkit-wpe/layout-test-results/imported/w3c/web-platform-tests/fetch/api/request/request-cache-reload-actual.txt
@@ -5,10 +5,10 @@
 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 
-PASS RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and fresh response 
+FAIL RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Etag and fresh response assert_equals: expected 2 but got 3
+FAIL RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and fresh response assert_equals: expected 2 but got 3


--- /home/dpino/workspace/webkit-wpe/layout-test-results/imported/w3c/web-platform-tests/fetch/api/request/request-cache-default-expected.txt
+++ /home/dpino/workspace/webkit-wpe/layout-test-results/imported/w3c/web-platform-tests/fetch/api/request/request-cache-default-actual.txt
@@ -1,8 +1,8 @@

 PASS RequestCache "default" mode checks the cache for previously cached content and goes to the network for stale responses with Etag and stale response
 PASS RequestCache "default" mode checks the cache for previously cached content and goes to the network for stale responses with Last-Modified and stale response
-PASS RequestCache "default" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Etag and fresh response 
-PASS RequestCache "default" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Last-Modified and fresh response 
+FAIL RequestCache "default" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Etag and fresh response assert_equals: expected 1 but got 2
+FAIL RequestCache "default" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Last-Modified and fresh response assert_equals: expected 1 but got 2
 PASS Responses with the "Cache-Control: no-store" header are not stored in the cache with Etag and stale response  
 PASS Responses with the "Cache-Control: no-store" header are not stored in the cache with Last-Modified and stale response 
 PASS Responses with the "Cache-Control: no-store" header are not stored in the cache with Etag and fresh response 

--- /home/dpino/workspace/webkit-wpe/layout-test-results/imported/w3c/web-platform-tests/fetch/api/request/request-cache-force-cache-expected.txt
+++ /home/dpino/workspace/webkit-wpe/layout-test-results/imported/w3c/web-platform-tests/fetch/api/request/request-cache-force-cache-actual.txt
@@ -1,8 +1,8 @@

-PASS RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for stale responses with Etag and stale response 
-PASS RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for stale responses with Last-Modified and stale response 
-PASS RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Etag and fresh response 
-PASS RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Last-Modified and fresh response 
+FAIL RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for stale responses with Etag and stale response assert_equals: expected 1 but got 2
+FAIL RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for stale responses with Last-Modified and stale response assert_equals: expected 1 but got 2
+FAIL RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Etag and fresh response assert_equals: expected 1 but got 2
+FAIL RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Last-Modified and fresh response assert_equals: expected 1 but got 2
 PASS RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Etag and stale response
 PASS RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Last-Modified and stale response
 PASS RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Etag and fresh response 
@@ -13,6 +13,6 @@
 PASS RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Last-Modified and fresh response 
 PASS RequestCache "force-cache" stores the response in the cache if it goes to the network with Etag and stale response 
 PASS RequestCache "force-cache" stores the response in the cache if it goes to the network with Last-Modified and stale response 
-PASS RequestCache "force-cache" stores the response in the cache if it goes to the network with Etag and fresh response 
-PASS RequestCache "force-cache" stores the response in the cache if it goes to the network with Last-Modified and fresh response 
+FAIL RequestCache "force-cache" stores the response in the cache if it goes to the network with Etag and fresh response assert_equals: expected 1 but got 2
+FAIL RequestCache "force-cache" stores the response in the cache if it goes to the network with Last-Modified and fresh response assert_equals: expected 1 but got 2

--- /home/dpino/workspace/webkit-wpe/layout-test-results/imported/w3c/web-platform-tests/fetch/api/basic/conditional-get-expected.txt
+++ /home/dpino/workspace/webkit-wpe/layout-test-results/imported/w3c/web-platform-tests/fetch/api/basic/conditional-get-actual.txt
@@ -1,3 +1,3 @@

-PASS Testing conditional GET with ETags 
+FAIL Testing conditional GET with ETags assert_equals: expected (string) "304" but got (object) null

-- 
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/20200311/ddabee8b/attachment-0001.htm>