Bug 94002 - [chromium] inspector/debugger tests flaky timeout on Win7 only
Summary: [chromium] inspector/debugger tests flaky timeout on Win7 only
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Windows 7
: P2 Normal
Assignee: Nobody
Depends on:
Reported: 2012-08-14 10:55 PDT by Adrienne Walker
Modified: 2013-04-05 13:01 PDT (History)
5 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Adrienne Walker 2012-08-14 10:55:11 PDT
See: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=inspector%2Fdebugger

Many inspector/debugger layout tests infrequently time out on Win7 (only).  This seems different than bug 90488, as the tests aren't always slow, just every once in a while it gets timed out but the other runs are fast.

Is this due to a race condition somewhere that is causing these tests not to complete?
Comment 1 Adrienne Walker 2012-08-14 10:58:32 PDT
Committed r125582: <http://trac.webkit.org/changeset/125582>
Comment 2 Vsevolod Vlasov 2012-11-07 09:31:35 PST
Only happens in debug: http://trac.webkit.org/changeset/133767
Comment 3 James Robinson 2013-03-11 15:42:11 PDT
(In reply to comment #2)
> Only happens in debug: http://trac.webkit.org/changeset/133767

No, it happens in release too and on non-win7 bots.  It's just a buggy test.  Example failure:

--- /mnt/data/b/build/slave/WebKit_Linux_32/build/layout-test-results/inspector/debugger/xhr-breakpoints-expected.txt
+++ /mnt/data/b/build/slave/WebKit_Linux_32/build/layout-test-results/inspector/debugger/xhr-breakpoints-actual.txt
@@ -1,22 +1,12 @@
 Tests XHR breakpoints.
-Debugger was enabled.
+error: Exception during test execution: TypeError: Cannot read property 'sidebarPanes' of undefined,TypeError: Cannot read property 'sidebarPanes' of undefined
+    at test (evaluateInWebInspector1.js:17:43)
+    at runTestInFrontend (evaluateInWebInspector1.js:10:13)
+    at eval (evaluateInWebInspector1.js:15:7)
+    at eval (native)
+    at Object.invokeMethod (file:///mnt/data/b/build/slave/WebKit_Linux_32/build/src/out/Release/resources/inspector/DevTools.js:48165:21)
+    at Object.InspectorBackendClass.runAfterPendingDispatches (file:///mnt/data/b/build/slave/WebKit_Linux_32/build/src/out/Release/resources/inspector/DevTools.js:5073:13)
+    at Object.InspectorBackendClass.dispatch (file:///mnt/data/b/build/slave/WebKit_Linux_32/build/src/out/Release/resources/inspector/DevTools.js:5015:6)
+    at Object.InspectorFrontendAPI.dispatchMessage (file:///mnt/data/b/build/slave/WebKit_Linux_32/build/src/out/Release/resources/inspector/DevTools.js:5782:18)
-Running: testXHRBreakpoint
-Script execution paused.
-Call stack:
-    0) sendRequest (xhr-breakpoints.html:11)
-    1)  (:1)
-Script execution resumed.
-Running: testPauseOnAnyXHR
-Script execution paused.
-Script execution resumed.
-Script execution paused.
-Script execution resumed.
-Running: testDisableBreakpoint
-Script execution paused.
-Script execution resumed.
-Debugger was disabled.
Comment 4 James Robinson 2013-03-11 15:42:20 PDT
*** Bug 99389 has been marked as a duplicate of this bug. ***
Comment 5 Timothy Hatcher 2013-04-05 13:01:20 PDT
Chromium and V8 have left the building. Won't fix.