external/wpt/service-workers/service-worker/fetch-event.https.html is flaky |
||||
Issue descriptionhttps://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_tests&tests=external%2Fwpt%2Fservice-workers%2Fservice-worker%2Ffetch-event.https.html fetch-event.https.html is very flaky across all platforms. Sample diff: --- /b/rr/tmpUzVt3O/w/layout-test-results/external/wpt/service-workers/service-worker/fetch-event.https-expected.txt +++ /b/rr/tmpUzVt3O/w/layout-test-results/external/wpt/service-workers/service-worker/fetch-event.https-actual.txt @@ -1,4 +1,5 @@ This is a testharness.js-based test. +Harness Error. harness_status.status = 1 , harness_status.message = assert_equals: Service Worker should respond to fetch with the correct type expected "reload" but got "default" PASS Service Worker responds to fetch event with string PASS Service Worker responds to fetch event with blob body PASS Service Worker responds to fetch event with the referrer URL Assigning to falken@ for further triage. I'll go ahead and disable the test in the meantime.
,
Apr 18 2017
This is weird, we expect the failed assert but sometimes additionally get: Harness Error. harness_status.status = 1 , harness_status.message = assert_equals: Service Worker should respond to fetch with the correct type expected "no-store" but got "default" in the output which causes the expected.txt file to not match. So this looks like some test runner issue with WPT tests? Not sure if it's related but we always get the following in stderr: CONSOLE ERROR: line 84: Mixed Content: The page at 'https://web-platform.test:8444/service-workers/service-worker/fetch-event.https.html' was loaded over HTTPS, but requested an insecure resource 'http://web-platform.test:8001/service-workers/service-worker//resources/simple.html?referrerFull'. This request has been blocked; the content must be served over HTTPS.
,
Apr 18 2017
Nevermind, I think I see. The test was accidentally creating tests outside the async_test system. Patch coming.
,
Apr 18 2017
,
Apr 18 2017
,
Apr 19 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/20784f77e32bcfea4e305ec28e532ed3e43c2116 commit 20784f77e32bcfea4e305ec28e532ed3e43c2116 Author: falken <falken@chromium.org> Date: Wed Apr 19 05:56:38 2017 fetch-event.https.html: Fix asserts mistakenly outside the promise chain This was causing flaky test output. BUG= 712264 Review-Url: https://codereview.chromium.org/2826573004 Cr-Commit-Position: refs/heads/master@{#465505} [modify] https://crrev.com/20784f77e32bcfea4e305ec28e532ed3e43c2116/third_party/WebKit/LayoutTests/TestExpectations [modify] https://crrev.com/20784f77e32bcfea4e305ec28e532ed3e43c2116/third_party/WebKit/LayoutTests/external/wpt/service-workers/service-worker/fetch-event.https-expected.txt [modify] https://crrev.com/20784f77e32bcfea4e305ec28e532ed3e43c2116/third_party/WebKit/LayoutTests/external/wpt/service-workers/service-worker/fetch-event.https.html
,
Apr 19 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Apr 17 2017