(After fixing bug 614231, this error is revealed.) http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1290560923.1290562190.31822.gz OS X 10.6 comm-central-trunk debug test reftest on 2010/11/23 17:08:43 { REFTEST TEST-UNEXPECTED-FAIL | file:///builds/slave/comm-central-trunk-macosx64-debug-unittest-reftest/build/reftest/tests/layout/reftests/font-matching/synthetic-bold-2.html | image comparison (!=) }

Ftr, our MacOSX 32bit is green: http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1290575069.1290576371.2502.gz&fulltext=1 OS X 10.5 comm-central-trunk debug test reftest on 2010/11/23 21:04:29 { REFTEST TEST-PASS | file:///builds/slave/comm-central-trunk-macosx-debug-unittest-reftest/build/reftest/tests/layout/reftests/font-matching/synthetic-bold-2.html | image comparison (!=) }

There already was something "odd" on m-c Try at first: see bug 538730 comment 9. Is there any way to figure out what is different between Firefox and SeaMonkey OS X 10.6 slaves? (I assume this test does not depend on hardware acceleration or webgl, does it?)

(In reply to comment #2) > Is there any way to figure out what is different between Firefox and SeaMonkey > OS X 10.6 slaves? Ours are build machines, theirs are talos machines, but both should be similar in most things (both are from the same class of minis, AFAIK) - though they might have some stuff there to fake that a screen is actually plugged in while we don't and probably won't ever have a chance to get that.

This test is still failing.

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1325879470.1325882628.31874.gz OS X 10.6 comm-central-trunk debug test reftest on 2012/01/06 11:51:10 Bug still there.

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