Closed Bug 692717 Opened 13 years ago Closed 12 years ago

Intermittent test_smilAccessKey.xhtml | application timed out after 330 seconds with no output

Categories

(Core :: SVG, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=6716810&tree=Mozilla-Inbound
Rev3 WINNT 5.1 mozilla-inbound debug test mochitests-1/5 on 2011-10-06 19:00:28 PDT for push b2ac6a043d78

79017 INFO TEST-START | /tests/content/smil/test/test_smilAccessKey.xhtml
--DOMWINDOW == 149 (0CA9A610) [serial = 2479] [outer = 00000000] [url = http://mochi.test:8888/tests/content/media/test/test_video_to_canvas.html]
TEST-UNEXPECTED-FAIL | /tests/content/smil/test/test_smilAccessKey.xhtml | application timed out after 330 seconds with no output

(followed by the current pathetic and unrelated way we can't kill the process on WinXP)
(disregard comment 1 -- it was a real test-regression (perma-orange) from bug 704482's first landing)
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.