Bug 101195 – Web Inspector: Flakyness in http/tests/inspector/network/network-initiator-from-console.html

• Component: Web Inspector (Deprecated)
• Status: RESOLVED FIXED

[Raphael Kubo da Costa (:rakuco)]

This is mostly about the EFL-WK2 port; the test is already skipped by a few ports, but there are no related bug reports in their TestExpectations files so I don't know if they have the same issue.

Every once in a while, http/tests/inspector/network/network-initiator-from-console.html fails on the bot (it's easier for me to reproduce it locally) because the console message indicating script.js has been loaded is not printed:

--- /tmp/wk-ltr-tmp/http/tests/inspector/network/network-initiator-from-console-expected.txt
+++ /tmp/wk-ltr-tmp/http/tests/inspector/network/network-initiator-from-console-actual.txt
@@ -1,4 +1,3 @@
-CONSOLE MESSAGE: line 1: Done.
 Tests that there is no javascript error when console evaluation causes resource loading.
 
 Bug 65466

After some debugging, it looks like InspectorTest.completeTest() is called before the request to script.js is fully processed, so the call to console.log("Done.") is made after InspectorTest.completeTest() has already teared everything down.

It happens much more often if Xvfb is used to run WebKitTestRunner: when the running X session is used instead, everything goes as expected and the call to WebInspector.panel("network").show() seems to "block" until script.js is fully processed. Speaking of that, using setTimeout(InspectorTest.completeTest, 0) instead of a direct call to that function seems to solve the problem with Xvfb.

I'm not very familiar with the inspector area of WebKit, but I'd be more than glad to help with this one.

[Vsevolod Vlasov]

Committed r133595: <http://trac.webkit.org/changeset/133595>