1292953 - Intermittent TEST-UNEXPECTED-TIMEOUT | devtools/client/inspector/markup/test/browser_markup_links_07.js | application timed out after 330 seconds with no output

Status: RESOLVED INCOMPLETE

(DevTools :: Inspector, defect, P3)

Description

[Treeherder Bug Filer]

Filed by: philringnalda [at] gmail.com

https://treeherder.mozilla.org/logviewer.html#?job_id=1502999&repo=autoland

http://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-macosx64-debug/1470430641/autoland_yosemite_r7-debug_test-mochitest-e10s-devtools-chrome-2-bm136-tests1-macosx-build43.txt.gz

Comment 1

[Julian Descottes [:jdescottes]]

Inspector bug triage, filter on CLIMBING SHOES.

Rare intermittent, P3.

Comment 2

[Alexandre Poirot [:ochameau]]

Both this bug and bug 1292952 links to the same failure.

Comment 3

[Alexandre Poirot [:ochameau]]

It looks like it times out during addTab, while waiting for load event on the <xul:browser> element:
15:30:01     INFO -  7623 INFO TEST-START | devtools/client/inspector/markup/test/browser_markup_links_07.js
15:30:01     INFO -  7624 INFO Entering test bound
15:30:01     INFO -  7625 INFO Adding a new tab with URL: http://example.com/browser/devtools/client/inspector/markup/test/doc_markup_links.html
15:30:01     INFO -  7626 INFO Waiting for event: 'load' on [object XULElement].

Which is what 99.9% do. So this is surprising.

I also see a lot of dom windows being detroyed while waiting for the load event.
Could it be related to GC issues being fixed in bug 1281341?

Also see bug 1300822 where I should fixes issues around load event wait. But I don't expect it to fix this particular intermittent.