Bug 148688 – [Win] http/tests/inspector/dom/disconnect-dom-tree-after-main-frame-navigation.html fails

• Status: REOPENED
• Component: Web Inspector

[Jeremy Jones]

The following layout test is failing on Windows

http/tests/inspector/dom/disconnect-dom-tree-after-main-frame-navigation.html

Probable cause:

Seems that inspector tests are timing out on Windows.

[Radar WebKit Bug Importer]

<rdar://problem/22526529>

[Jeremy Jones]

Created attachment 260383 [details]
Patch

[Build Bot]

Comment on attachment 260383 [details]
Patch

Attachment 260383 [details] did not pass mac-ews (mac):
Output: http://webkit-queues.webkit.org/results/130939

New failing tests:
http/tests/w3c/dom/nodes/ParentNode-querySelector-All.html

[Build Bot]

Created attachment 260387 [details]
Archive of layout-test-results from ews101 for mac-mavericks

The attached test failures were seen while running run-webkit-tests on the mac-ews.
Bot: ews101  Port: mac-mavericks  Platform: Mac OS X 10.9.5

[Joseph Pecoraro]

Comment on attachment 260383 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=260383&action=review

> LayoutTests/platform/win/TestExpectations:2374
> +webkit.org/b/137157 http/tests/inspector/dom/disconnect-dom-tree-after-main-frame-navigation.html [ Skip ]

I'm guessing win should just skip all http/tests/inspector at this point. It skips all non-http inspector tests.

[Chris Dumez]

(In reply to comment #3)
> Comment on attachment 260383 [details]
> Patch
> 
> Attachment 260383 [details] did not pass mac-ews (mac):
> Output: http://webkit-queues.webkit.org/results/130939
> 
> New failing tests:
> http/tests/w3c/dom/nodes/ParentNode-querySelector-All.html

Sorry about that. This is a flake and I marked it as so in <https://trac.webkit.org/r189235>.

[WebKit Commit Bot]

Comment on attachment 260383 [details]
Patch

Clearing flags on attachment: 260383

Committed r189237: <http://trac.webkit.org/changeset/189237>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Alexey Proskuryakov]

Re-opening, because this simply skipped the test, and didn't fix it.

[Blaze Burg]

No inspector tests should be running on Windows, as the DRT/WKTR hooks are currently broken. This particular result was caused because http/tests/inspector was not added as Skip when I marked all the other inspector tests as Skip.

Re-enabling inspector tests on Windows is blocked on my getting access to a Windows machine, and is tracked by the following bugs:

https://bugs.webkit.org/show_bug.cgi?id=148037
https://bugs.webkit.org/show_bug.cgi?id=148025