[ Mac WK2 iOS Sim ] Layout Test imported/w3c/web-platform-tests/mediacapture-record/MediaRecorder-stop.html is a flaky failure

• Component: Tools / Tests
• Status: NEW ---

[Shawn Roberts]

The following layout test is failing on Mac WK2 Release and Debug, iOS Simulator Release and Debug

imported/w3c/web-platform-tests/mediacapture-record/MediaRecorder-stop.html

Probable cause:

Test has been flaky its entire history on the dashboard. Local testing fails on on various versions from when the test was imported in https://trac.webkit.org/changeset/237311/webkit and reported flaky then.

Test was modified and fixed in https://trac.webkit.org/changeset/237642/webkit and reported flaky then as well.

Test recently started showing up in iOS queue's, but testing with older revisions for iOS up until r237642 fail as well.

Fails on average 2 times in 500 iterations.

Reproduced with :

run-webkit-tests imported/w3c/web-platform-tests/mediacapture-record/MediaRecorder-stop.html --iterations 500 -f

Flakiness Dashboard:

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2Fmediacapture-record%2FMediaRecorder-stop.html

Diff:

--- /Volumes/Data/slave/ios-simulator-12-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/mediacapture-record/MediaRecorder-stop-expected.txt
+++ /Volumes/Data/slave/ios-simulator-12-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/mediacapture-record/MediaRecorder-stop-actual.txt
@@ -1,4 +1,6 @@
+
+Harness Error (TIMEOUT), message = null
 
 PASS MediaRecorder will stop recording and fire a stop event when all tracks are ended 
-PASS MediaRecorder will stop recording and fire a stop event when stop() is called 
+TIMEOUT MediaRecorder will stop recording and fire a stop event when stop() is called Test timed out

[Radar WebKit Bug Importer]

<rdar://problem/49429677>

[Shawn Roberts]

Marked flaky in https://trac.webkit.org/changeset/243659/webkit

[youenn fablet]

*** Bug 217538 has been marked as a duplicate of this bug. ***