Closed
Bug 547613
Opened 14 years ago
Closed 14 years ago
mochitest-plain: Test timed out on tests/content/media/test/test_ended1.html
Categories
(Core :: Audio/Video, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: alqahira, Unassigned)
References
Details
(Keywords: intermittent-failure)
After landing the patch for bug 541743, WINNT 5.2 mozilla-central debug test mochitests-1/5 (s: win32-slave09) had an unexpected fail via timeout on test/content/media/test/test_ended1.html http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1266790645.1266792790.23269.gz It doesn't immediately resolve to any known orange bugs that I or anyone in #developers could see (the closest, bug 493647, is a different failure in a similar test) and no one in #developers at the time had any other ideas, but offhand it also doesn't look like it's related to the patch for bug 541743, either. nthomas kicked off a couple additional cycles of that testset.
Blocks: 438871
Reporter | ||
Comment 1•14 years ago
|
||
(In reply to comment #0) > nthomas kicked off a couple additional cycles of that testset. These were green, so either this bug is a dupe of another random-orange bug that I couldn't find and no one else could, or it's a new random orange. :P
Comment 2•14 years ago
|
||
Given that the code the patch for bug 541743 touches is not used in Firefox at the moment, I strongly doubt it could possibly lead to this test failure. ;)
Comment 3•14 years ago
|
||
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1267496679.1267500333.25156.gz WINNT 5.2 mozilla-central debug test mochitests-1/5 on 2010/03/01 18:24:39 s: win32-slave08
Comment 4•14 years ago
|
||
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1269270928.1269273202.14952.gz
Updated•14 years ago
|
Whiteboard: [orange]
Comment 5•14 years ago
|
||
No recent occurrences.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•12 years ago
|
Keywords: intermittent-failure
Assignee | ||
Updated•12 years ago
|
Whiteboard: [orange]
You need to log in
before you can comment on or make changes to this bug.
Description
•