Bug 306124

Summary: [macOS Debug] 2 tests in TestWebKitAPI.WebKit2.CaptureMute are flaky
Product: WebKit Reporter: Marta Darbinyan <darbinyan>
Component: MediaAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Marta Darbinyan
Reported 2026-01-23 10:27:27 PST
The following tests is timing out on EWS bots across different PRs in re-runs. On main the timeouts are less frequent. TestWebKitAPI.WebKit2.CaptureMuteAPI 09:34:31.191 25151 TestWebKitAPI.WebKit2.CaptureMuteAPI 09:34:31.191 25151 2026-01-23 09:27:37.679 TestWebKitAPI[47342:539669] NSEventConcurrentProcessingEnabled=NO 09:34:31.191 25151 2026-01-23 09:27:38.516 TestWebKitAPI[47342:539669] Encountered error: Error Domain=WKErrorDomain Code=4 "A JavaScript exception occurred" UserInfo={WKJavaScriptExceptionLineNumber=22, WKJavaScriptExceptionMessage=TypeError: null is not an object (evaluating 'stream.getTracks'), WKJavaScriptExceptionColumnNumber=23, WKJavaScriptExceptionSourceURL=file:///Volumes/Data/worker/macOS-Tahoe-Debug-API-Tests-EWS/build/WebKitBuild/Debug/TestWebKitAPIResources.bundle/Contents/Resources/getUserMedia.html, NSLocalizedDescription=A JavaScript exception occurred} while evaluating script: stop() Test history: https://results.webkit.org/?suite=api-tests&test=TestWebKitAPI.WebKit2.CaptureMuteAPI&style=debug Test result: https://ews-build.webkit.org/#/builders/165/builds/7457
Attachments
Radar WebKit Bug Importer
Comment 1 2026-01-23 10:27:46 PST
EWS
Comment 2 2026-01-23 12:17:54 PST
Test gardening commit 306113@main (9e34498753df): <https://commits.webkit.org/306113@main> Reviewed commits have been landed. Closing PR #57136 and removing active labels.
EWS
Comment 3 2026-01-26 15:04:13 PST
Test gardening commit 306248@main (5ab3d5015933): <https://commits.webkit.org/306248@main> Reviewed commits have been landed. Closing PR #57280 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.