194916 2019-02-21 13:51:39 -0800 fast/mediastream/MediaStream-video-element.html is flaky 2019-04-19 22:12:48 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=194829 InRadar P2 Normal --- 1 cdumez webkit-unassigned ap eric.carlson jer.noble lforschler rniwa tsavell webkit-bug-importer youennf oldest_to_newest 1508648 0 cdumez 2019-02-21 13:51:39 -0800 fast/mediastream/MediaStream-video-element.html is flaky: --- /Volumes/Data/slave/highsierra-release-tests-wk2/build/layout-test-results/fast/mediastream/MediaStream-video-element-expected.txt +++ /Volumes/Data/slave/highsierra-release-tests-wk2/build/layout-test-results/fast/mediastream/MediaStream-video-element-actual.txt @@ -47,7 +47,7 @@ video.audioTracks[0] properties: track.id = <UUID> track.kind = main - track.label = Mock audio device 1 + track.label = track.language = 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 1508649 1 cdumez 2019-02-21 13:52:55 -0800 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. 1508650 2 cdumez 2019-02-21 13:54:08 -0800 This started with https://trac.webkit.org/changeset/241821 which avoids re-constructing a new WKContext / WebProcessPool between tests whenever possible. 1509464 3 webkit-bug-importer 2019-02-24 08:41:14 -0800 <rdar://problem/48345402> 1509645 4 tsavell 2019-02-25 09:05:07 -0800 Marked test as failing to get the tree green while waiting on resolution: https://trac.webkit.org/changeset/242044/webkit 1519939 5 cdumez 2019-03-21 14:27:28 -0700 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. 1519941 6 cdumez 2019-03-21 14:28:58 -0700 The test is relying on a setTimeout(100): function canplay() { debug("<br>*** start playback ****"); evalAndLog("video.play()"); setTimeout(checkVideoElement, 100); } :/ 1529040 7 rniwa 2019-04-19 22:12:48 -0700 This test appears to be always failing now?÷