Closed Bug 603842 Opened 14 years ago Closed 12 years ago

reftest/tests/image/test/reftest/pngsuite-basic-n/basn0g16.html | timed out waiting for onload to fire (followed by reftest failure in basn0g16.png)

Categories

(Core :: Layout: Tables, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dholbert, Unassigned)

References

()

Details

(Keywords: intermittent-failure)

REFTEST TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/mozilla-central_leopard-old-debug_test-reftest/build/reftest/tests/modules/libpr0n/test/reftest/pngsuite-basic-n/basn0g16.html | timed out waiting for onload to fire
REFTEST INFO | Loading a blank page
++DOMWINDOW == 43 (0x23580828) [serial = 146] [outer = 0x2023e310]
WARNING: Flushing retained layers!: file /builds/slave/mozilla-central-macosx-debug/build/layout/base/nsLayoutUtils.cpp, line 1422
REFTEST TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/mozilla-central_leopard-old-debug_test-reftest/build/reftest/tests/modules/libpr0n/test/reftest/pngsuite-basic-n/basn0g16.png |
REFTEST   IMAGE 1 (TEST): data:image/png;base64,[---OMITTED BY DHOLBERT FOR BREVITY---]
REFTEST   IMAGE 2 (REFERENCE): data:image/png;base64,[---OMITTED BY DHOLBERT FOR BREVITY---]
REFTEST number of differing pixels: 1007

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1286924677.1286926379.10985.gz
Rev3 MacOSX Leopard 10.5.8 mozilla-central debug test reftest on 2010/10/12 16:04:37
s: talos-r3-leopard-015

The reference case (the html file) is blank, in the reftest snapshot. (not surprising, given the warning message saying that it timed out.
The reference case here (the one that timed out before firing onload) is:
http://mxr.mozilla.org/mozilla-central/source/modules/libpr0n/test/reftest/pngsuite-basic-n/basn0g16.html?force=1

Note that there's no script there --  it's just a 32x32 HTML table, each cell 1px in size and having its own color.

While I was initially tempted to say "it just timed out because it's complex," I don't think that's actually the case.  The reftest timeout that expired is 5 minutes[1], which is a really long time for even a page to take to load (even a 32x32 table).

[1] http://mxr.mozilla.org/mozilla-central/source/layout/tools/reftest/runreftest.py?mark=201-204#201
If it was the reference that timed out and not the PNG, then this is a DOM bug, no?
Not necessarily DOM (more likely to be table layout, probably).  But yeah, not an imagelib bug.
Component: ImageLib → Layout: Tables
QA Contact: imagelib → layout.tables
Summary: reftest/tests/modules/libpr0n/test/reftest/pngsuite-basic-n/basn0g16.html | timed out waiting for onload to fire (followed by reftest failure in basn0g16.png) → reftest/tests/image/test/reftest/pngsuite-basic-n/basn0g16.html | timed out waiting for onload to fire (followed by reftest failure in basn0g16.png)
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.