Bug 78819 – [GTK] fast/workers/shared-worker-load-error.html times out

• Component: WebKitGTK
• Status: NEW

[Philippe Normand]

I don't know since when, a bisect would be needed. Diff:

--- /home/slave/webkitgtk/gtk-linux-64-release/build/layout-test-results/fast/workers/shared-worker-load-error-expected.txt 
+++ /home/slave/webkitgtk/gtk-linux-64-release/build/layout-test-results/fast/workers/shared-worker-load-error-actual.txt 
@@ -1,6 +1,5 @@
+FAIL: Timed out waiting for notifyDone to be called
 Test SharedWorker onerror functionality. Prints multiple SUCCESS lines, then DONE when complete.
 
 PASS: Received load error event: [object Event]
-PASS: Received error event after worker GC'd: [object Event]
-DONE

[Zan Dobersek]

Created attachment 159722 [details]
Patch

[Zan Dobersek]

Comment on attachment 159722 [details]
Patch

Urgh, wrong bug.

[Zan Dobersek]

This test still flakily times out.
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=fast%2Fworkers%2Fshared-worker-load-error

The timeout occurs due to the SharedWorker being garbage-collected after set to null before the second load error is fired. When the error event does fire, there are no event listeners so the onerror callback does not get called so the test doesn't stop.

The test is skipped on EFL. It's skipped on Chromium as well, but for other reasons. I'll unskip it on EFL to get more data, though I'm not sure how the failure could be platform-dependent, i.e. given it also fails on EFL, I don't see how (presumably) the libsoup backend could have an effect here.