Bug 272256 - REGRESSION [ iOS ] 3X TestWebKitAPI.WKNavigation are timing out
Summary: REGRESSION [ iOS ] 3X TestWebKitAPI.WKNavigation are timing out
Status: RESOLVED DUPLICATE of bug 272669
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2024-04-05 16:24 PDT by Jay Stfleur
Modified: 2024-04-17 09:19 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jay Stfleur 2024-04-05 16:24:28 PDT 
Description:
TestWebKitAPI.WKNavigation.AutomaticHiddenViewDelayedReloadAfterWebProcessCrash
TestWebKitAPI.WKNavigation.AutomaticVisibleViewReloadAfterWebProcessCrash 
TestWebKitAPI.WKNavigation.ProcessCrashDuringCallback 

are a constant timing out Since SDK 21E180.
TestWebKitAPI.WKNavigation.ProcessCrashDuringCallback is flaky on release but is consistent on Debug.


History:
https://results.webkit.org/?suite=api-tests&suite=api-tests&suite=api-tests&test=TestWebKitAPI.WKNavigation.AutomaticHiddenViewDelayedReloadAfterWebProcessCrash&test=TestWebKitAPI.WKNavigation.AutomaticVisibleViewReloadAfterWebProcessCrash&test=TestWebKitAPI.WKNavigation.ProcessCrashDuringCallback&platform=ios

Command to reproduce for all 3 tests:
run-api-tests --root --ios-simulator --debug TestWebKitAPI.WKNavigation.AutomaticVisibleViewReloadAfterWebProcessCrash
Comment 1 Radar WebKit Bug Importer 2024-04-05 16:24:50 PDT 
<rdar://problem/125995768>
Comment 2 Ryan Haddad 2024-04-17 09:16:42 PDT 
These timeouts were resolved somewhere in this range http://commits.webkit.org/compare/277512@main...277506@main
Comment 3 Ryan Haddad 2024-04-17 09:19:03 PDT 
Maybe it was fixed by this? 

WebKit process termination with xpc_connection_kill does not always work
https://commits.webkit.org/277509@main?

*** This bug has been marked as a duplicate of bug 272669 ***