253452 2023-03-06 11:24:50 -0800 REGRESSION (260774@main): [ iOS 16 ] media/muted-video-is-playing-audio.html is flaky timeout. 2023-03-07 11:03:31 -0800 1 1 1 Unclassified WebKit New Bugs Other Unspecified Unspecified RESOLVED DUPLICATE 253035 InRadar P2 Normal --- 1 bharris9 webkit-unassigned jer.noble webkit-bot-watchers-bugzilla webkit-bug-importer oldest_to_newest 1939185 0 bharris9 2023-03-06 11:24:50 -0800 media/muted-video-is-playing-audio.html is a flaky timeout on iOS 16 release running on Intel only. HISTORY: https://results.webkit.org/?suite=layout-tests&test=media%2Fmuted-video-is-playing-audio.html I was able to replicate this timeout at iOS 16 ToT as follows: run-webkit-tests --ios-simulator media/muted-video-is-playing-audio.html DIFF TEXT: @@ -1,3 +1,5 @@ +FAIL: Timed out waiting for notifyDone to be called + Testing that muting a video element should result in page's audio playing state to become false On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". @@ -5,10 +7,6 @@ PASS window.internals.pageMediaState().includes('IsPlayingAudio') became true PASS window.internals.pageMediaState().includes('IsPlayingAudio') became false -PASS window.internals.pageMediaState().includes('IsPlayingAudio') became true -PASS successfullyParsed is true - -TEST COMPLETE RUN(video.muted = true) RUN(video.muted = false) 1939187 1 bharris9 2023-03-06 11:26:18 -0800 Although first timeout was shown at 260776@main. I was able to replicate the timeout on 260774@main but not at 260771@main as follows: run-webkit-tests --ios-simulator media/muted-video-is-playing-audio.html This brings a possible regression range of 260772@main-260774@main. 1939188 2 webkit-bug-importer 2023-03-06 11:26:41 -0800 <rdar://problem/106309394> 1939193 3 bharris9 2023-03-06 11:37:36 -0800 Update to initial comment: test is flaky timeout on Apple Silicon but a constant timeout on Intel. I was able to replicate timeouts on both Apple Silicon and Intel the same way as listed prior. 1939246 4 ryanhaddad 2023-03-06 14:19:19 -0800 https://commits.webkit.org/260774@main seems to be the most likely candidate. 1939500 5 ryanhaddad 2023-03-07 10:43:38 -0800 https://commits.webkit.org/261295@main may have fixed this 1939513 6 ryanhaddad 2023-03-07 11:03:31 -0800 *** This bug has been marked as a duplicate of bug 253035 ***