[Webkit-unassigned] [Bug 242136] New: [ macOS Release ] TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchingNetworkProcessData is a flaky timeout

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=242136

            Bug ID: 242136
           Summary: [ macOS Release ]
                    TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchi
                    ngNetworkProcessData is a flaky timeout
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: rackler at apple.com

Description:
TestWebKitAPI.WebKit.CustomDataStoreDestroyWhileFetchingNetworkProcessData

The first failure that I saw on the dashboard was on 2/21/2022 at 247607 at 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 at main.  

REPRODUCTION STEPS
On 251957 at 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

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220629/2f8a23e0/attachment.htm>