RESOLVED CONFIGURATION CHANGED 216634
[ macOS wk2 ] imported/w3c/web-platform-tests/service-workers/service-worker/fetch-waits-for-activate.https.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=216634
Summary [ macOS wk2 ] imported/w3c/web-platform-tests/service-workers/service-worker/...
Hector Lopez
Reported 2020-09-16 19:55:21 PDT
imported/w3c/web-platform-tests/service-workers/service-worker/fetch-waits-for-activate.https.html Test is a flaky failure according to history on macOS w2. First occurrence of failure us at r254144 but no indication revision was cause. History: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fservice-workers%2Fservice-worker%2Ffetch-waits-for-activate.https.html&platform=mac&limit=50000 Diff: --- /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/fetch-waits-for-activate.https-expected.txt +++ /Volumes/Data/slave/catalina-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/service-workers/service-worker/fetch-waits-for-activate.https-actual.txt @@ -1,4 +1,4 @@ PASS Navigation fetch events should wait for the activate event to complete. -PASS Subresource fetch events should wait for the activate event to complete. +FAIL Subresource fetch events should wait for the activate event to complete. assert_equals: active worker should be in activated state expected "activated" but got "activating" Note, similar Diff to this: https://bugs.webkit.org/show_bug.cgi?id=181392
Attachments
Radar WebKit Bug Importer
Comment 1 2020-09-16 19:55:45 PDT
Hector Lopez
Comment 2 2020-09-16 19:59:31 PDT
Test expectation while investigated: https://trac.webkit.org/changeset/267179/webkit
youenn fablet
Comment 3 2022-11-09 01:50:07 PST
Not flaky anymore
Ryan Haddad
Comment 4 2022-11-09 09:30:29 PST
We need to remove the flaky test expectations.
Ryan Haddad
Comment 5 2022-11-09 09:31:46 PST
Expectations were removed in https://commits.webkit.org/256483@main
Note You need to log in before you can comment on or make changes to this bug.