Intermittent test_DOMWindowCreated.xul | application timed out after 330 seconds with no output

RESOLVED WORKSFORME

Status

()

Core
DOM
RESOLVED WORKSFORME
5 years ago
5 years ago

People

(Reporter: philor, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86_64
Mac OS X
intermittent-failure
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
https://tbpl.mozilla.org/php/getParsedLog.php?id=21766558&tree=Mozilla-Inbound
Rev4 MacOSX Lion 10.7 mozilla-inbound debug test mochitest-other on 2013-04-12 16:36:55 PDT for push 278d87108cb0
slave: talos-r4-lion-019

23:44:29     INFO -  4368 INFO TEST-START | chrome://mochitests/content/chrome/dom/tests/mochitest/chrome/test_DOMWindowCreated.xul
23:44:30     INFO -  ++DOMWINDOW == 60 (0x1432a62a8) [serial = 1406] [outer = 0x1157e7188]
23:44:30     INFO -  ++DOCSHELL 0x143b6a350 == 13 [id = 245]
23:44:30     INFO -  ++DOMWINDOW == 61 (0x11854a6a8) [serial = 1407] [outer = 0x0]
23:44:30     INFO -  ++DOMWINDOW == 62 (0x118e14af8) [serial = 1408] [outer = 0x11854a6a8]
23:44:30     INFO -  ++DOCSHELL 0x142c88b00 == 14 [id = 246]
23:44:30     INFO -  ++DOMWINDOW == 63 (0x142cac4a8) [serial = 1409] [outer = 0x0]
23:50:00  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/dom/tests/mochitest/chrome/test_DOMWindowCreated.xul | application timed out after 330 seconds with no output

https://tbpl.mozilla.org/php/getParsedLog.php?id=21794004&tree=Fx-Team
Rev4 MacOSX Lion 10.7 fx-team debug test mochitest-other on 2013-04-14 09:01:56 PDT for push 7143c88f59dc
slave: talos-r4-lion-066

16:09:00     INFO -  4368 INFO TEST-START | chrome://mochitests/content/chrome/dom/tests/mochitest/chrome/test_DOMWindowCreated.xul
16:09:00     INFO -  ++DOMWINDOW == 64 (0x113b3ace8) [serial = 1406] [outer = 0x11b5e5c08]
16:09:00     INFO -  ++DOCSHELL 0x142c7e0c0 == 13 [id = 245]
16:09:00     INFO -  ++DOMWINDOW == 65 (0x11201db98) [serial = 1407] [outer = 0x0]
16:09:00     INFO -  ++DOMWINDOW == 66 (0x1120952c8) [serial = 1408] [outer = 0x11201db98]
16:09:00     INFO -  ++DOCSHELL 0x11303b990 == 14 [id = 246]
16:09:00     INFO -  ++DOMWINDOW == 67 (0x1428bb4f8) [serial = 1409] [outer = 0x0]
16:14:30  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/dom/tests/mochitest/chrome/test_DOMWindowCreated.xul | application timed out after 330 seconds with no output

Curiously, the screenshots for those two failures on two different 10.7 slaves both show a missing Dock.
Comment hidden (Treeherder Robot)
(In reply to Phil Ringnalda (:philor) from comment #0)
> Curiously, the screenshots for those two failures on two different 10.7
> slaves both show a missing Dock.

The screenshot for the failure in comment 1 shows no dock, too, FWIW. (Is that unusual? On my local mac, I have the dock configured to auto-hide, but I take it that's not the case on our test runners?)
(Reporter)

Comment 3

5 years ago
Four possibilities: we always have done auto-hide, and I forgot; we accidentally switched to it; we used to stick the mouse where it would cause it to show despite auto-hide and now we don't; we're crashing the Dock.
Comment hidden (Treeherder Robot)
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.