Bug 252850 - REGRESSION (260575@main?): [ iOS Release ] TestWebKitAPI.WKWebViewCloseAllMediaPresentations.VideoFullscreen is a consistent timeout
Summary: REGRESSION (260575@main?): [ iOS Release ] TestWebKitAPI.WKWebViewCloseAllMed...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2023-02-23 11:40 PST by Bri Harris
Modified: 2023-05-11 16:08 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bri Harris 2023-02-23 11:40:22 PST
TestWebKitAPI.WKWebViewCloseAllMediaPresentations.VideoFullscreen

is a flaky timeout on iOS 16 only. 


HISTORY:

https://results.webkit.org/?suite=api-tests&test=TestWebKitAPI.WKWebViewCloseAllMediaPresentations.VideoFullscreen


TIMEOUT ERROR:

TestWebKitAPI.WKWebViewCloseAllMediaPresentations.VideoFullscreen
        2023-02-23 10:13:10.597 TestWebKitAPI[38829:25202454] Encountered error: Error Domain=WKErrorDomain Code=5 "JavaScript execution returned a result of an unsupported type" UserInfo={NSLocalizedDescription=JavaScript execution returned a result of an unsupported type} while evaluating script: window.internals.setMockVideoPresentationModeEnabled(true)
Comment 1 Bri Harris 2023-02-23 11:47:52 PST
I was able to reproduce this time out on a release build as follows:

run-api-tests --ios-simulator --root WebKitBuild/Release-iphonesimulator TestWebKitAPI.WKWebViewCloseAllMediaPresentations.VideoFullscreen
Comment 2 Radar WebKit Bug Importer 2023-02-23 11:48:13 PST
<rdar://problem/105844731>
Comment 3 Ryan Haddad 2023-02-27 11:36:53 PST
This timeout appears to be consistent on iPhone simulator release queues. https://commits.webkit.org/260575@main is in the regression range, and seems like it could be related.
Comment 4 Ryan Haddad 2023-03-07 10:46:01 PST
This test is no longer timing out as of 261100@main, but I don't see an obvious change to credit with fixing it.