Closed Bug 579139 Opened 15 years ago Closed 12 years ago

intermittent orange - image/test/mochitest/test_bug478398.html | image should have been discarded!

Categories

(Core :: Graphics: ImageLib, defect)

Product:
Core
Component:
Graphics: ImageLib
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking2.0 --- -

People

(Reporter: bholley, Assigned: joe)

References

Details

(Keywords: intermittent-failure)

This test ran with the possible-buggy timer changes from bug 558306, so this may be collateral damage.
(In reply to comment #1) > This test ran with the possible-buggy timer changes from bug 558306, so this > may be collateral damage. That makes sense. This test is pretty timer-dependent. I'll wait to see how that plays out and if this keeps happening.
Blocks: 438871
Whiteboard: [orange]
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1280241205.1280242536.31245.gz WINNT 5.2 mozilla-central debug test mochitests-4/5 on 2010/07/27 07:33:25
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1280246421.1280248800.25794.gz#err0 WINNT 5.2 mozilla-central debug test mochitests-4/5 on 2010/07/27 09:00:21
Disabled this test - I don't think we're getting much benefit by leaving it on. Joe's going to look into it with record-and-replay soon. http://hg.mozilla.org/mozilla-central/rev/bd6899480d92
blocking2.0: --- → betaN+
Assigning to Joe since according to comment #31 he's going to be looking into it soon.
Assignee: nobody → joe
Timeout-based test failures don't need to block, IMO.
blocking2.0: betaN+ → -
FWIW, this test consistently fails on my machine now.
Summary: intermittent orange - modules/libpr0n/test/mochitest/test_bug478398.html | image should have been discarded! → intermittent orange - image/test/mochitest/test_bug478398.html | image should have been discarded!
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.