WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED CONFIGURATION CHANGED
242136
[ macOS Release ] TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchingNetworkProcessData is a flaky timeout
https://bugs.webkit.org/show_bug.cgi?id=242136
Summary
[ macOS Release ] TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchingNet...
Karl Rackler
Reported
2022-06-29 14:02:29 PDT
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
Attachments
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2022-06-29 14:02:46 PDT
<
rdar://problem/96166439
>
Sihui Liu
Comment 2
2023-06-13 14:39:39 PDT
The test is no longer timed out on bots according to results dashboard.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug