Bug 193989 - Layout Test http/wpt/service-workers/fetchEvent.https.html is flaky
Summary: Layout Test http/wpt/service-workers/fetchEvent.https.html is flaky
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-29 15:13 PST by Shawn Roberts
Modified: 2019-04-03 14:47 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shawn Roberts 2019-01-29 15:13:35 PST
The following layout test is flaky on Mojave WK2

http/wpt/service-workers/fetchEvent.https.html

Probable cause:

Unable to duplicate locally. Either by running test singly or bisecting from this test and back it will not fail locally.

Flakiness Dashboard:

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Fwpt%2Fservice-workers%2FfetchEvent.https.html

Diff:

--- /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/http/wpt/service-workers/fetchEvent.https-expected.txt
+++ /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/http/wpt/service-workers/fetchEvent.https-actual.txt
@@ -1,10 +1,5 @@
+#PID UNRESPONSIVE - com.apple.WebKit.WebContent.Development (pid 5482)
+FAIL: Timed out waiting for notifyDone to be called
 
-PASS Setup worker 
-PASS FetchEvent respondWith should throw if called twice 
-PASS FetchEvent request is SameObject 
-PASS FetchEvent should be in error if responding with undefined 
-PASS FetchEvent should be in error if not responding with a Response 
-PASS FetchEvent should be in error if responding with a Promise that does not resolve to a Response 
-PASS FetchEvent should be in error if responding with a Promise that rejects 
-PASS FetchEvent should resolve when responding with a Response 
-
+#EOF
+#EOF
Comment 1 Shawn Roberts 2019-04-03 14:47:23 PDT
Test is not showing up as a failure on dashboard any longer. 
Closing bug