fast/mediastream/getUserMedia-to-canvas-2.html is a constant time out on iOS 16 and macOS. HISTORY: https://results.webkit.org/?suite=layout-tests&test=fast%2Fmediastream%2Fmock-media-source-webaudio.html DIFF TEXT: @@ -1,17 +1,4 @@ +CONSOLE MESSAGE: A MediaStreamTrack ended due to a capture failure +FAIL: Timed out waiting for notifyDone to be called -PASS func: withWebGL, angle: 90, imageBitmap: false, subImage: false, unpackFlipY: true -PASS func: withWebGL, angle: 90, imageBitmap: false, subImage: true, unpackFlipY: false -PASS func: withWebGL, angle: 90, imageBitmap: false, subImage: true, unpackFlipY: true -PASS func: withWebGL, angle: 90, imageBitmap: true, subImage: false, unpackFlipY: false -PASS func: withWebGL, angle: 90, imageBitmap: true, subImage: false, unpackFlipY: true -PASS func: withWebGL, angle: 90, imageBitmap: true, subImage: true, unpackFlipY: false -PASS func: withWebGL, angle: 90, imageBitmap: true, subImage: true, unpackFlipY: true -PASS func: withWebGL, angle: 180, imageBitmap: false, subImage: false, unpackFlipY: false -PASS func: withWebGL, angle: 180, imageBitmap: false, subImage: false, unpackFlipY: true -PASS func: withWebGL, angle: 180, imageBitmap: false, subImage: true, unpackFlipY: false -PASS func: withWebGL, angle: 180, imageBitmap: false, subImage: true, unpackFlipY: true -PASS func: withWebGL, angle: 180, imageBitmap: true, subImage: false, unpackFlipY: false -PASS func: withWebGL, angle: 180, imageBitmap: true, subImage: false, unpackFlipY: true -PASS func: withWebGL, angle: 180, imageBitmap: true, subImage: true, unpackFlipY: false -PASS func: withWebGL, angle: 180, imageBitmap: true, subImage: true, unpackFlipY: true
I was able to reproduce this time out on iOS 16 ToT as follows: run-webkit-tests fast/mediastream/getUserMedia-to-canvas-2.html
<rdar://problem/106432559>
CORRECTED HISTORY LINK: https://results.webkit.org/?suite=layout-tests&test=fast%2Fmediastream%2FgetUserMedia-to-canvas-2.html
https://commits.webkit.org/261455@main appears to have resolved the consistent timeout. The test is still a flaky timeout, but that appears to have been pre-existing. *** This bug has been marked as a duplicate of bug 253632 ***