DevTools: cleanup debugger tests.

LayoutTests/http/tests/inspector/inspector-test.js

Index: LayoutTests/http/tests/inspector/inspector-test.js
diff --git a/LayoutTests/http/tests/inspector/inspector-test.js b/LayoutTests/http/tests/inspector/inspector-test.js
index 85e1c1844e2fc9e26e8584678fd577d6b77e3888..00374d5667398547f9ffae7376ed227de6fec289 100644
--- a/LayoutTests/http/tests/inspector/inspector-test.js
+++ b/LayoutTests/http/tests/inspector/inspector-test.js
@@ -696,9 +696,7 @@ function didEvaluateForTestInFrontend(callId)
     delete window.completeTestCallId;
     if (outputElement && window.quietUntilDone)
         outputElementParent.appendChild(outputElement);
-    // Close inspector asynchrously to allow caller of this
-    // function send response before backend dispatcher and frontend are destroyed.
-    setTimeout(closeInspectorAndNotifyDone, 0);

[yurys, 2014/06/06 08:59:58]

I wonder why we needed this before but not now? Was it added for the when
testRunner.closeWebInspector worked synchronously?

[loislo, 2014/06/06 12:41:13]

I think it is a bit strange behavior when test asked the harness to close the
inspector before it got everything it expected from the inspected page. Such
kind of tests are flaky by design.

[pfeldman, 2014/06/06 13:24:15]

i think yurys@ is right here and since closeInspector is now async, this change
is okay to make.

@loislo: comment above explains exactly why this was so. it seems like your
comment here suggests that you are confusing things.

+    closeInspectorAndNotifyDone();
 }
 
 function closeInspectorAndNotifyDone()