Bug 51398 - [Chromium] inspector/console-dir-global.html and inspector/debugger-expand-scope.html are timing out on OSX
Summary: [Chromium] inspector/console-dir-global.html and inspector/debugger-expand-sc...
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-21 07:40 PST by Andrei Popescu
Modified: 2013-04-09 16:10 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Popescu 2010-12-21 07:40:47 PST
In  http://trac.webkit.org/changeset/74390/

a change was introduced that causes inspector/console-dir-global.html and inspector/debugger-expand-scope.html layout tests to time out on OSX.

See the first canary that picked up the change:

http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Mac/builds/1988

I will update test_expectations.txt for now, until we work out what the problem is.
Comment 1 Yuta Kitamura 2010-12-21 08:11:22 PST
This is strange, because:

- My change does not touch any inspector code; I just added a call to ScriptExecutionContext::addMessage(), and this does not happen in normal code paths (you need to create a WebSocket and cause a network error).

- I added a new console test under http/tests/inspector, but this test should be skipped on Mac and Linux (http://crbug.com/26734).

- These two tests should also be skipped on Mac and Linux.
Comment 2 Yuta Kitamura 2010-12-21 08:29:34 PST
My wild guess is that the new test console-websocket-error.html timeouts for some reason (and this is not shown in the bots for some reason) and the following tests are affected by this timeout.

But these tests should not be executed in the first place...
Comment 3 Andrei Popescu 2010-12-21 10:15:40 PST
Hi,

(In reply to comment #2)
> My wild guess is that the new test console-websocket-error.html timeouts for some reason (and this is not shown in the bots for some reason) and the following tests are affected by this timeout.
> 
> But these tests should not be executed in the first place...

I agree this is all unclear but it's definitely true that the tests were passing before your change. Why exactly should they not be executed in the first place?

Would you mind if we or you rolled out your change just to verify the correlation with the failing tests?
Comment 4 Yuta Kitamura 2010-12-21 17:13:41 PST
They should not be executed because inspector tests are skipped on Mac and Linux.

// Add support for inspector layout tests on non-Windows.
BUGCR26734 LINUX MAC SKIP : inspector = PASS
BUGCR26734 LINUX MAC SKIP : http/tests/inspector = PASS
BUGCR26734 LINUX MAC SKIP : http/tests/inspector-enabled = PASS
Comment 5 Yuta Kitamura 2010-12-22 04:45:02 PST
A patch in bug 51380 may fix this.
Comment 6 Stephen Chenney 2013-04-09 16:10:30 PDT
LayoutTest failures for Chromium are being marked WontFix. The Bug is still accessible and referenced from TestExpectations.