--- /b/rr/tmpKwCSBB/w/layout-test-results/external/wpt/fetch/api/request/request-cache-reload-expected.txt
+++ /b/rr/tmpKwCSBB/w/layout-test-results/external/wpt/fetch/api/request/request-cache-reload-actual.txt
@@ -1,14 +1,14 @@
 This is a testharness.js-based test.
-FAIL RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Etag and stale response assert_equals: expected (undefined) undefined but got (string) "\"0.8193642670453274\""
-FAIL RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and stale response assert_equals: expected (undefined) undefined but got (string) "Mon, 27 Mar 2017 11:24:51 GMT"
+FAIL RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Etag and stale response assert_equals: expected (undefined) undefined but got (string) "\"0.4121166660151836\""
+FAIL RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and stale response assert_equals: expected (undefined) undefined but got (string) "Tue, 24 Oct 2017 06:31:40 GMT"
 FAIL RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Etag and fresh response assert_equals: expected 2 but got 1
 FAIL RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and fresh response assert_equals: expected 2 but got 1
 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 even if a previous response is already stored with Etag and stale response assert_equals: expected (undefined) undefined but got (string) "\"0.8205498946141332\""
-FAIL RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and stale response assert_equals: expected (undefined) undefined but got (string) "Mon, 27 Mar 2017 11:24:51 GMT"
+FAIL RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Etag and stale response assert_equals: expected (undefined) undefined but got (string) "\"0.3845144814231636\""
+FAIL RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and stale response assert_equals: expected (undefined) undefined but got (string) "Tue, 24 Oct 2017 06:31:40 GMT"
 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 1
 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 1
 Harness: the test ran to completion.
