fast/mediastream/MediaStream-video-element.html is flaky:
@@ -47,7 +47,7 @@
track.id = <UUID>
track.kind = main
- track.label = Mock audio device 1
+ track.label =
track.enabled = true
track.sourceBuffer = null
Steps to reproduce:
run-webkit-tests fast/mediastream/MediaStream-video-element-video-tracks-disabled.html fast/mediastream/MediaStream-video-element.html --child-processes 1
This is somehow related to using a different WebView for the 2 tests but the same WKContext/WebProcessPool. I am not super familiar with this code. I spent some time trying to understand the mock media devices code yesterday but could not figure out the issue.
This started with https://trac.webkit.org/changeset/241821 which avoids re-constructing a new WKContext / WebProcessPool between tests whenever possible.
Marked test as failing to get the tree green while waiting on resolution:
You can reproduce it with the test by itself:
Tools/Scripts/run-webkit-tests fast/mediastream/MediaStream-video-element.html -gf --repeat-each=50
So it is a flaky test and r241821 merely impacted the timing of things, making the test flakier.
The test is relying on a setTimeout(100):
debug("<br>*** start playback ****");
This test appears to be always failing now?÷