Intermittent layout/reftests/svg/smil/event/event-end-1.svg | timed out waiting for pending paint count to reach zero (waiting for MozAfterPaint)

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
8 years ago
7 years ago

People

(Reporter: philor, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
macOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1294172453.1294173628.3710.gz
Rev3 MacOSX Leopard 10.5.8 mozilla-central opt test reftest on 2011/01/04 12:20:53
s: talos-r3-leopard-006

REFTEST TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/svg/smil/event/event-end-1.svg | timed out waiting for pending paint count to reach zero (waiting for MozAfterPaint)
(Reporter)

Comment 1

8 years ago
(There's more, a great deal more, really a whole lot more, in the log, but the snippet for just this test is 5MB, and thus over the attachment size limit.)
Ah yes, apparently there's tons of "REFTEST INFO |" lines for failing tests now. Thankfully, that all compresses well, so zip brings it down from 5MB to 24KB :)

In case it's useful, here's the (zipped) snippet of the log from the start of this reftest to just before the start of the next one.
Ah -- it looks like it's just tons of repeated content.  What follows is the content immediately after the UNEXPECTED-FAIL line from comment 0...
{
REFTEST INFO | Saved log: START file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/svg/smil/event/event-end-1.svg
REFTEST INFO | Saved log: OnDocumentLoad triggering WaitForTestEnd
REFTEST INFO | Saved log: WaitForTestEnd: Adding listeners
REFTEST INFO | Saved log: DoDrawWindow 0,0,800,1000
REFTEST INFO | Saved log: MakeProgress: STATE_WAITING_TO_FIRE_INVALIDATE_EVENT
REFTEST INFO | Saved log: MakeProgress: waiting for MozAfterPaint
REFTEST INFO | Saved log: AfterPaintListener in file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/svg/smil/event/event-end-1.svg
REFTEST INFO | Saved log: AfterPaintListener in chrome://reftest/content/reftest.xul
REFTEST INFO | Saved log: DoDrawWindow 0,0,800,1000
REFTEST INFO | Saved log: MakeProgress: STATE_WAITING_TO_FIRE_INVALIDATE_EVENT
REFTEST INFO | Saved log: MakeProgress: waiting for MozAfterPaint
REFTEST INFO | Saved log: AfterPaintListener in file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/svg/smil/event/event-end-1.svg
REFTEST INFO | Saved log: AfterPaintListener in chrome://reftest/content/reftest.xul
REFTEST INFO | Saved log: DoDrawWindow 0,0,100,100
REFTEST INFO | Saved log: MakeProgress: STATE_WAITING_TO_FIRE_INVALIDATE_EVENT
REFTEST INFO | Saved log: MakeProgress: waiting for MozAfterPaint
REFTEST INFO | Saved log: AfterPaintListener in file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/svg/smil/event/event-end-1.svg
REFTEST INFO | Saved log: AfterPaintListener in chrome://reftest/content/reftest.xul
REFTEST INFO | Saved log: DoDrawWindow 0,0,100,100
}
... and after this, everything between the "DoDrawWindow 0,0,100,100" lines just repeats endlessly.
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
Comment hidden (Legacy TBPL/Treeherder Robot)
(Reporter)

Comment 15

8 years ago
I'm betting that comment 14, where the harness admits to feeling kind of guilty about how it maybe caused the error, is not totally unrelated to the others.
Comment hidden (Legacy TBPL/Treeherder Robot)
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
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.