Bug 225816 – REGRESSION(r277313): [ Debug ] 2 TestWebKitAPI.IPCTestingAPI (API-Tests) are constant timeouts

• Status: RESOLVED
• Resolution: FIXED
• Component: New Bugs

[Robert Jenner]

The following two TestWebKitAPI.IPCTestingAPI are constant timeouts on Catalina, BigSur, and iOS14-Simulator Debug:

TestWebKitAPI.IPCTestingAPI.CanReceiveIPCSemaphore
TestWebKitAPI.IPCTestingAPI.CanReceiveSharedMemory

HISTORY:
https://results.webkit.org/?suite=api-tests&suite=api-tests&test=TestWebKitAPI.IPCTestingAPI.CanReceiveIPCSemaphore&test=TestWebKitAPI.IPCTestingAPI.CanReceiveSharedMemory

Both APIs have the same history. It appears they both started timing out constantly at r277313. Working on reproduction steps.

[Robert Jenner]

I have reproduced the timeout at BigSur Debug ToT using the following test:

run-api-tests TestWebKitAPI.IPCTestingAPI.CanReceiveIPCSemaphore


I was also able to verify the regression point. The timeouts did occur at r277313, but did not occur at r277312. So it appears r277313 caused the regression.

[Radar WebKit Bug Importer]

<rdar://problem/78025515>

[Sam Weinig]

Ok, we just need to update the names of some messages from ImageData to PixelBuffer.

These tests are really error prone and will likely see more of this kind of failure if we don’t have a more robust way to catch these failures at compile time or at least better errors when the signatures don’t match at runtime.

[Sam Weinig]

Created attachment 428648 [details]
Patch

[EWS]

Committed r277506 (237737@main): <https://commits.webkit.org/237737@main>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 428648 [details].