Bug 223074

Summary: [ macOS Debug wk2 arm64 ] 7 webrtc/video layout tests are flakey timing out
Product: WebKit Reporter: Robert Jenner <jenner>
Component: WebRTCAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: webkit-bot-watchers-bugzilla, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=223043
Attachments:
Description Flags
Timeout diffs none

Robert Jenner
Reported 2021-03-11 09:50:35 PST
The following 7 webrtc tests are flakey timeouts in BigSur Debug wk2 on Apple Silicon only: webrtc/video-rotation-no-cvo.html webrtc/video-rotation.html webrtc/video-setDirection.html webrtc/video-sframe.html webrtc/video-unmute.html webrtc/video-with-data-channel.html webrtc/video.html HISTORY URL: https://results.webkit.org/?suite=layout-tests&suite=layout-tests&suite=layout-tests&suite=layout-tests&suite=layout-tests&suite=layout-tests&suite=layout-tests&test=webrtc%2Fvideo-rotation-no-cvo.html&test=webrtc%2Fvideo-rotation.html&test=webrtc%2Fvideo-setDirection.html&test=webrtc%2Fvideo-sframe.html&test=webrtc%2Fvideo-unmute.html&test=webrtc%2Fvideo-with-data-channel.html&test=webrtc%2Fvideo.html&architecture=arm64 All of these tests have very similar histories in the sense that they all started flakey timing out when they started to run on Debug on Apple Silicon Macs. It should be noted that the timeouts are flakey, but they occur more often than not.
Attachments
Timeout diffs (8.49 KB, application/zip)
2021-03-11 09:55 PST, Robert Jenner
no flags
Radar WebKit Bug Importer
Comment 1 2021-03-11 09:50:53 PST
Robert Jenner
Comment 2 2021-03-11 09:55:19 PST
Created attachment 422940 [details] Timeout diffs Attaching all 7 diffs for the tests that are timing out.
Robert Jenner
Comment 3 2021-03-11 09:56:23 PST
I cannot reproduce these failures because they only occur in Debug on Apple Silicon Macs, and I do not have access to one of those systems.
Note You need to log in before you can comment on or make changes to this bug.