Bug 239309

Summary:	[ iOS ] TestWebKitAPI.WebKit2.CrashGPUProcessWhileCapturingAndCalling is a flaky timeout
Product:	WebKit	Reporter:	Dawn Morningstar <Morningstar>
Component:	New Bugs	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED DUPLICATE
Severity:	Normal	CC:	hhjalmarsson, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified
See Also:	https://bugs.webkit.org/show_bug.cgi?id=239315

Dawn Morningstar

Reported 2022-04-13 15:46:05 PDT

TestWebKitAPI.WebKit2.CrashGPUProcessWhileCapturingAndCalling is a flaky timeout on iOS queues HISTORY: https://results.webkit.org/?suite=api-tests&test=TestWebKitAPI.WebKit2.CrashGPUProcessWhileCapturingAndCalling TIMEOUT: TestWebKitAPI.WebKit2.CrashGPUProcessWhileCapturingAndCalling 2022-04-13 12:57:41.115 TestWebKitAPI[1073:761224] Writing analzed variants. (webrtc_video_engine.cc:3482): Absent receive stream; ignoring clearing encoded frame sink for ssrc 0 MessageReceiveQueueMap::addImpl - adding duplicate any id receiver 35 MessageReceiveQueueMap::addImpl - adding duplicate any id receiver 31 2022-04-13 12:57:43.357 TestWebKitAPI[1073:761224] Encountered error: Error Domain=WKErrorDomain Code=4 "A JavaScript exception occurred" UserInfo={WKJavaScriptExceptionLineNumber=1, WKJavaScriptExceptionMessage=ReferenceError: Can't find variable: checkDecodingVideo, WKJavaScriptExceptionColumnNumber=19, WKJavaScriptExceptionSourceURL=undefined, NSLocalizedDescription=A JavaScript exception occurred} while evaluating script: checkDecodingVideo() STDIO-URL: https://ews-build.webkit.org/#/builders/9/builds/69156/steps/24/logs/stdio

Attachments
Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2022-04-13 15:46:43 PDT

<rdar://problem/91719743>

Dawn Morningstar

Comment 2 2022-04-13 19:24:35 PDT

Disabling test to help EWS r292852

Hercules Hjalmarsson

Comment 3 2022-08-01 10:49:38 PDT

Duplicate *** This bug has been marked as a duplicate of bug 239315 ***

Note You need to log in before you can comment on or make changes to this bug.