REOPENED 187484
Layout Test imported/w3c/web-platform-tests/service-workers/service-worker/update-after-navigation-fetch-event.https.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=187484
Summary Layout Test imported/w3c/web-platform-tests/service-workers/service-worker/up...
Truitt Savell
Reported 2018-07-09 14:26:05 PDT
The following layout test is flaky on Mac Platforms imported/w3c/web-platform-tests/service-workers/service-worker/update-after-navigation-fetch-event.https.html Probable cause: I do not know Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2Fservice-workers%2Fservice-worker%2Fupdate-after-navigation-fetch-event.https.html
Attachments
Update test expectations. (1.38 KB, patch)
2018-07-09 14:34 PDT, Truitt Savell
no flags
Truitt Savell
Comment 1 2018-07-09 14:34:33 PDT
Created attachment 344618 [details] Update test expectations.
WebKit Commit Bot
Comment 2 2018-07-09 17:09:20 PDT
Comment on attachment 344618 [details] Update test expectations. Clearing flags on attachment: 344618 Committed r233669: <https://trac.webkit.org/changeset/233669>
WebKit Commit Bot
Comment 3 2018-07-09 17:09:21 PDT
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 4 2018-07-09 17:10:23 PDT
Dawei Fenton (:realdawei)
Comment 5 2018-07-11 09:20:57 PDT
re-opening because this only marked the test as flaky.
Truitt Savell
Comment 6 2018-07-11 10:16:17 PDT
Test Diff of failure: --- /Volumes/Data/slave/highsierra-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/update-after-navigation-fetch-event.https-expected.txt +++ /Volumes/Data/slave/highsierra-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/update-after-navigation-fetch-event.https-actual.txt @@ -1,3 +1,6 @@ -PASS Update should be triggered after a navigation fetch event. +Harness Error (TIMEOUT), message = null + +TIMEOUT Update should be triggered after a navigation fetch event. Test timed out + Failure has been occurring ever 5-10 runs on at least one of the platforms.
Note You need to log in before you can comment on or make changes to this bug.