All (or alsmot all) Web inspector related tests timeout in debug builds, from at least since december-2019. GTK debug bot has been aborting early since then.
I have marked all Web inspector related tests as slow in r257051 for Debug. I was going to mark them as timing out, but I decided to give them a run locally to check if in slow they passed and most of them did. I just marked as timing out the ones that timed out locally. Will check on the Debug bot after the next run if there are more timing outs and if needed mark them as timing out if this continues to be an issue.
See also bug 149916
Ok, the debug bot has stopped exiting early due to this unexpected timeouts, and we now most of the inspector tests are completing the run in debug, just marked as slow so the testrunner gives them extra time to run. There are still some issues with the Web inspector tests there on the last run. Many giving text failure, one timeout and one crash. https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Debug%20%28Tests%29/builds/5941
Created attachment 421387 [details] WIP patch
Created attachment 421437 [details] WIP patch
Comment on attachment 421437 [details] WIP patch View in context: https://bugs.webkit.org/attachment.cgi?id=421437&action=review > Source/WebInspectorUI/UserInterface/Protocol/MessageDispatcher.js:33 > + const timeLimitPerRunLoop = 100; // milliseconds This code was add by Bug 135427 (r171881). It is very old. There should be any recent changes increasing processing time.
Created attachment 421864 [details] WIP patch WI.dispatchNextQueuedMessageFromBackend is using setTimeout, but it is very slow because it is throttled by 1 second.
This is a bug ticket for Mac. Bug 147456 – LayoutTests/inspector frequently run slow and timeout when run in WebKit2 but not WebKit1
Created attachment 421896 [details] Patch
Comment on attachment 421896 [details] Patch Clearing flags on attachment: 421896 Committed r273724 (234739@main): <https://commits.webkit.org/234739@main>
All reviewed patches have been landed. Closing bug.
<rdar://problem/74912815>
*** Bug 149916 has been marked as a duplicate of this bug. ***
Looks like the Windows client is also missing this switch. Any way we could make this more cross platform?