Bug 194624 – [ Mac WK2 ] REGRESSION (r233720) Layout Test http/wpt/resource-timing/rt-cors.worker.html is a flaky failure

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: Tools / Tests

[Shawn Roberts]

The following layout test is flaky on Mac WK2

http/wpt/resource-timing/rt-cors.worker.html

Probable cause:

Test became a flaky failure with r233720 . 

Reproducible with:

run-webkit-tests t233720 http/wpt/resource-timing/rt-cors.worker.html --iterations  1500 -f --exit-after-n-failures=1 --no-retry-failures

Flakiness Dashboard:

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Fwpt%2Fresource-timing%2Frt-cors.worker.html

Diff: 

--- /Volumes/Data/slave/mojave-debug-tests-wk2/build/layout-test-results/http/wpt/resource-timing/rt-cors.worker-expected.txt
+++ /Volumes/Data/slave/mojave-debug-tests-wk2/build/layout-test-results/http/wpt/resource-timing/rt-cors.worker-actual.txt
@@ -1,26 +1,5 @@
+#PID UNRESPONSIVE - com.apple.WebKit.WebContent.Development (pid 59851)
+FAIL: Timed out waiting for notifyDone to be called
 
-PASS Must have PerformanceObserver and PerformanceResourceTiming in DedicatedWorkerGlobalScope 
-PASS Same Origin request must have timing data 
-PASS Cross Origin resource without Timing-Allow-Origin must have filtered timing data 
-PASS Cross Origin resource with Timing-Allow-Origin null value must have filtered timing data 
-PASS Cross Origin resource with Timing-Allow-Origin wildcard must have timing data 
-PASS Cross Origin resource with origin in Timing-Allow-Origin list must have timing data (only entry) 
-PASS Cross Origin resource with origin in Timing-Allow-Origin list must have timing data (middle entry, comma separated) 
-PASS Cross Origin resource with origin in Timing-Allow-Origin list must have timing data (middle entry, multiple headers) 
-PASS Cross Origin resource with origin not in Timing-Allow-Origin list must have filtered timing data (other origins, comma separated) 
-PASS Cross Origin resource with origin not in Timing-Allow-Origin list must have filtered timing data (other origins, multiple headers) 
-PASS Cross Origin resource with origin not in Timing-Allow-Origin list must have filtered timing data (case-sensitive) 
-PASS Redirect to Same Origin request must have timing data 
-PASS Redirect to Cross Origin resource without Timing-Allow-Origin must have filtered timing data 
-PASS Redirect to Cross Origin resource with Timing-Allow-Origin null value must have filtered timing data 
-PASS Redirect to Cross Origin resource with Timing-Allow-Origin wildcard must have timing data 
-PASS Redirect to Cross Origin resource with origin in Timing-Allow-Origin list must have timing data (only entry) 
-PASS Redirect to Cross Origin resource with origin in Timing-Allow-Origin list must have timing data (middle entry, comma separated) 
-PASS Redirect to Cross Origin resource with origin in Timing-Allow-Origin list must have timing data (middle entry, multiple headers) 
-PASS Redirect to Cross Origin resource with origin not in Timing-Allow-Origin list must have filtered timing data (other origins, comma separated) 
-PASS Redirect to Cross Origin resource with origin not in Timing-Allow-Origin list must have filtered timing data (other origins, multiple headers) 
-PASS Redirect to Cross Origin resource with origin not in Timing-Allow-Origin list must have filtered timing data (case-sensitive) 
-PASS Multiple level redirect to Same Origin resource must have timing data 
-PASS Multiple level redirect to Cross Origin resource without Timing-Allow-Origin must have must have filtered timing data 
-PASS Multiple level redirect to Cross Origin resource with Timing-Allow-Origin must have must have timing data 
-
+#EOF
+#EOF

[Radar WebKit Bug Importer]

<rdar://problem/48058526>

[Shawn Roberts]

Test is no longer flaky on the dashboard. Closing bug as it's no longer valid.