Bug 262928

Summary:	REGRESSION(Sonoma): [ Sonoma ] 2 API tests under TestWebKitAPI.WebKit.* are constantly timing out.
Product:	WebKit	Reporter:	Ben Schwartz <ben_schwartz>
Component:	Tools / Tests	Assignee:	Elliott Williams <emw>
Status:	RESOLVED FIXED
Severity:	Normal	CC:	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=262065 https://bugs.webkit.org/show_bug.cgi?id=263020
Bug Depends on:	263020
Bug Blocks:

Description Ben Schwartz 2023-10-09 15:37:28 PDT

The following API tests are constantly timing out on macOS Sonoma:

TestWebKitAPI.WebKit.HTTPSProxyAPI
TestWebKitAPI.WebKit.SOCKS5API

HISTORY:

https://results.webkit.org/?suite=api-tests&suite=api-tests&test=TestWebKitAPI.WebKit.HTTPSProxyAPI&test=TestWebKitAPI.WebKit.SOCKS5API

REPRODUCIBILITY:

I was able to reproduce this issue on macOS Sonoma (14.0, 22G74/arm64) ToT using the following commands:

```
python3 Tools/CISupport/download-built-product --platform=mac --debug 'https://s3-us-west-2.amazonaws.com/archives.webkit.org/mac-sonoma-x86_64 arm64-debug/268614@main.zip'
python3 Tools/CISupport/built-product-archive --platform=mac-sonoma --debug extract
python3 Tools/Scripts/run-api-tests --no-build --json-output=api_test_results.json --debug --verbose TestWebKitAPI.WebKit.HTTPSProxyAPI TestWebKitAPI.WebKit.SOCKS5API
```

REGRESSION:

These tests have been constantly timing out since their introduction with the macOS Sonoma bring-up at 268549@main.

Comment 1 Radar WebKit Bug Importer 2023-10-09 15:37:48 PDT

<rdar://problem/116703485>

Comment 2 EWS 2023-10-10 21:06:52 PDT

Test gardening commit 269188@main (b5f962b54b6d): <https://commits.webkit.org/269188@main>

Reviewed commits have been landed. Closing PR #18872 and removing active labels.

Comment 3 Elliott Williams 2023-10-11 10:39:53 PDT

Pull request: https://github.com/WebKit/WebKit/pull/18949

Comment 4 Elliott Williams 2023-10-11 10:45:21 PDT

Nevermind, this is being fixed in https://bugs.webkit.org/show_bug.cgi?id=263020.