Description: TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchingNetworkProcessData The first failure that I saw on the dashboard was on 2/21/2022 at 247607@main. This test is a flaky timeout on Big Sur Release wk1 arm64 and Monterey Release wk2 arm64. Big Sur Release wk1 arm64 has been flaky for its entire history on the dashboard. Monterey Release wk2 arm64 I first see on 3/24/2022 at 251860@main. REPRODUCTION STEPS On 251957@main ToT, I get ASSERTION FAILED: RunLoop::isMain() every few iterations. It is unclear if this could be the cause of the flaky timeout. Command: run-api-tests --release --no-build --verbose --iterations 50 TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchingNetworkProcessData Result: ASSERTION FAILED: RunLoop::isMain() /Volumes/Data/worker/trunk-opensource-debug-archive/build/OpenSource/Source/WebKit/NetworkProcess/storage/NetworkStorageManager.cpp(156) : virtual WebKit::NetworkStorageManager::~NetworkStorageManager() History: https://results.webkit.org/?suite=api-tests&test=TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchingNetworkProcessData&platform=mac&limit=50000&architecture=arm64 run-api-tests stdio: Timeout TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchingNetworkProcessData
<rdar://problem/96166439>
The test is no longer timed out on bots according to results dashboard.