Bug 202747 - REGRESSION(r250357:r250365): [GTK] http/tests/cache-storage/cache-records-persistency.https.html is failing
Summary: REGRESSION(r250357:r250365): [GTK] http/tests/cache-storage/cache-records-per...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-09 06:30 PDT by Alicia Boya García
Modified: 2020-01-21 01:50 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alicia Boya García 2019-10-09 06:30:00 PDT
http/tests/cache-storage/cache-records-persistency.https.html

--- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/http/tests/cache-storage/cache-records-persistency.https-expected.txt
+++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/http/tests/cache-storage/cache-records-persistency.https-actual.txt
@@ -1,9 +1,7 @@
 
 PASS Cleaning existing caches 
-PASS Cache.put called twice with matching Requests - keys should remain the same - testing persistency 
+FAIL Cache.put called twice with matching Requests - keys should remain the same - testing persistency promise_test: Unhandled rejection with value: object "TypeError: undefined is not an object (evaluating 'result.text')"
 PASS Cleaning created caches 
-PASS Checking persistency of cache keys 
-PASS Checking persistency of response 
-PASS Checking persistency of response body 
-PASS Testing overriding of an existing cached record that is not in memory 
+FAIL Checking persistency of cache keys assert_equals: expected 1 but got 0
+FAIL Checking persistency of response assert_equals: Cache.put should store the response persistently expected "[object Response]" but got "[object Undefined]"
Comment 1 Diego Pino 2020-01-21 01:50:04 PST
Fixed by r254342.

Failure was removed from TestExpectations in r254824. There are no more failures referencing this ticket.