Closed
Bug 593245
Opened 14 years ago
Closed 9 years ago
[SeaMonkey, (Debug) Linux] reftest: "TEST-UNEXPECTED-FAIL | file:///.../546071-1-ref.html | Exited with code 1 during test run" after "ABORT: X_FreeColormap: BadColor (invalid Colormap parameter)"
Categories
(Core :: Web Painting, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
blocking2.0 | --- | - |
People
(Reporter: sgautherie, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, regression, Whiteboard: [test which aborts the suite])
http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey&maxdate=1282970579 http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1282959164.1282962023.26855.gz Linux comm-central-trunk debug test reftest on 2010/08/27 18:32:44 passes: { REFTEST TEST-START | file:///builds/slave/comm-central-trunk-linux-debug-unittest-reftest/build/reftest/tests/layout/reftests/bugs/546071-1.html Current scroll pos is 0, 0 For application/x-test found plugin libnptest.so REFTEST TEST-START | file:///builds/slave/comm-central-trunk-linux-debug-unittest-reftest/build/reftest/tests/layout/reftests/bugs/546071-1-ref.html Current scroll pos is 0, 0 NPP_Destroy WARNING: Unable to retrieve pref: plugins.unloadASAP: file /builds/slave/comm-central-trunk-linux-debug/build/mozilla/modules/plugin/base/src/nsPluginHost.cpp, line 316 For application/x-test found plugin libnptest.so REFTEST TEST-PASS | file:///builds/slave/comm-central-trunk-linux-debug-unittest-reftest/build/reftest/tests/layout/reftests/bugs/546071-1.html | } http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1282963632.1282964657.6065.gz&fulltext=1 Linux comm-central-trunk debug test reftest on 2010/08/27 19:47:12 crashes: { REFTEST TEST-START | file:///builds/slave/comm-central-trunk-linux-debug-unittest-reftest/build/reftest/tests/layout/reftests/bugs/546071-1.html For application/x-test found plugin libnptest.so REFTEST TEST-START | file:///builds/slave/comm-central-trunk-linux-debug-unittest-reftest/build/reftest/tests/layout/reftests/bugs/546071-1-ref.html ###!!! ABORT: X_FreeColormap: BadColor (invalid Colormap parameter); id=0x4145ec Re-running with MOZ_X_SYNC=1 in the environment may give a more helpful backtrace.: file /builds/slave/comm-central-trunk-linux-debug/build/mozilla/toolkit/xre/nsX11ErrorHandler.cpp, line 190 X11Error [toolkit/xre/nsX11ErrorHandler.cpp:191] libbonoboui-2.so.0 + 0x20445 ... ###!!! ABORT: X_FreeColormap: BadColor (invalid Colormap parameter); id=0x4145ec Re-running with MOZ_X_SYNC=1 in the environment may give a more helpful backtrace.: file /builds/slave/comm-central-trunk-linux-debug/build/mozilla/toolkit/xre/nsX11ErrorHandler.cpp, line 190 NEXT ERROR TEST-UNEXPECTED-FAIL | file:///builds/slave/comm-central-trunk-linux-debug-unittest-reftest/build/reftest/tests/layout/reftests/bugs/546071-1-ref.html | Exited with code 1 during test run INFO | automation.py | Application ran for: 0:16:05.202669 INFO | automation.py | Reading PID log: /tmp/tmpNpsiZypidlog PROCESS-CRASH | file:///builds/slave/comm-central-trunk-linux-debug-unittest-reftest/build/reftest/tests/layout/reftests/bugs/546071-1-ref.html | application crashed (minidump found) ... Thread 0 (crashed) 0 ld-2.5.so + 0x7f2 ... } Regression timeframe: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1cc78fe1f2cf&tochange=0886ad6e6aaa -> Timothy's push...
Reporter | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Comment 1•14 years ago
|
||
Does this only happen on tinderbox? Is is random or consistent?
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) It's consistent. I don't know if it happens on other computers.
Summary: [SeaMonkey, (Debug) Linux] "TEST-UNEXPECTED-FAIL | file:///.../546071-1-ref.html | Exited with code 1 during test run" after "ABORT: X_FreeColormap: BadColor (invalid Colormap parameter)" → [SeaMonkey, (Debug) Linux] reftest: "TEST-UNEXPECTED-FAIL | file:///.../546071-1-ref.html | Exited with code 1 during test run" after "ABORT: X_FreeColormap: BadColor (invalid Colormap parameter)"
Reporter | ||
Comment 3•14 years ago
|
||
http://brasstacks.mozilla.com/topfails/test/SeaMonkey?name=reftest/tests/layout/reftests/bugs/546071-1-ref.html confirms comment 0 regression timeframe :-) But also shows that this bug happened previously (last was 9 days before) +/- randomly: that might help to find/confirm what the cause is.
Comment 4•14 years ago
|
||
What's different about the seamonkey reftests from mozilla-central reftests? Is it just the machine they are running on on tinderbox?
Reporter | ||
Comment 5•14 years ago
|
||
(In reply to comment #4) The "machines", yes. And the application, of course. But nothing specific to reftest harness/suite, afaik.
Comment 6•14 years ago
|
||
(In reply to comment #4) > What's different about the seamonkey reftests from mozilla-central reftests? Is > it just the machine they are running on on tinderbox? Should be just the machine, I guess, as we're running tests on CentOS 5 (we can't afford large numbers of different machines to run Talos on Fedora). I don't think that not building libxul should make any difference for reftests, esp. as this only happens on one platform.
blocking2.0: ? → -
Comment 7•14 years ago
|
||
roc, would one of us (me or KaiRo) vnc-ing into the machine and taking a screenshot of both the ref and test page be helpful in solving this? I would really love not having reftest failures on our machines, since it *should* all be core code.
Comment 8•14 years ago
|
||
(In reply to comment #7) > roc, would one of us (me or KaiRo) vnc-ing into the machine and taking a > screenshot of both the ref and test page be helpful in solving this? > > I would really love not having reftest failures on our machines, since it > *should* all be core code. err, *crash* misread stuff, but I'd still like to assist in debugging/fixing anyway I can.
Comment 9•14 years ago
|
||
Questions that pop to mind: does it crash if you just run the 546071 reftest? If not what is the minimal set of reftests you need to run to see this crash?
Reporter | ||
Comment 10•14 years ago
|
||
(In reply to comment #9) > Questions that pop to mind: does it crash if you just run the 546071 reftest? > If not what is the minimal set of reftests you need to run to see this crash? Or we could try to find out the other way: does the suite still crash if we disable this reftest (for SeaMonkey)?
Comment 11•13 years ago
|
||
Are we still hitting this?
Reporter | ||
Comment 12•13 years ago
|
||
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #11) > Are we still hitting this? I can't tell atm: bug 711530 happens before this test is run :-/
Comment 13•9 years ago
|
||
Serge, can you still reproduce this in a recent build?
Flags: needinfo?(bugzillamozillaorg_serge_20140323)
Updated•9 years ago
|
Whiteboard: [test which aborts the suite] → [test which aborts the suite][closeme 2015-06-04]
Reporter | ||
Comment 14•9 years ago
|
||
(In reply to Serge Gautherie (:sgautherie) from comment #0) > http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey&maxdate=1282970579 Tinderbox doesn't seem to exist anymore. (In reply to Serge Gautherie (:sgautherie) from comment #3) > http://brasstacks.mozilla.com/topfails/test/SeaMonkey?name=reftest/tests/ > layout/reftests/bugs/546071-1-ref.html Topfails doesn't seem to exist anymore. What tools should I be using (nowadays), instead of these ones?
Flags: needinfo?(bugzillamozillaorg_serge_20140323) → needinfo?(mats)
Comment 15•9 years ago
|
||
(In reply to Serge Gautherie (:sgautherie) from comment #14) > (In reply to Serge Gautherie (:sgautherie) from comment #0) > > http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey&maxdate=1282970579 > > Tinderbox doesn't seem to exist anymore. It's been replaced with treeherder: https://treeherder.mozilla.org/ > (In reply to Serge Gautherie (:sgautherie) from comment #3) > > http://brasstacks.mozilla.com/topfails/test/SeaMonkey?name=reftest/tests/ > > layout/reftests/bugs/546071-1-ref.html > > Topfails doesn't seem to exist anymore. Perhaps replaced by: http://brasstacks.mozilla.com/orangefactor/ (if you need more info, please ask jmaher@)
Flags: needinfo?(mats)
Whiteboard: [test which aborts the suite][closeme 2015-06-04] → [test which aborts the suite]
Comment 16•9 years ago
|
||
There haven't been any reports on this for the past 5 years, so unless someone can produce evidence that it still occurs we should just close it as worksforme.
Whiteboard: [test which aborts the suite] → [test which aborts the suite][closeme 2015-10-21]
Comment 17•9 years ago
|
||
Resolved per whiteboard and Comment 16
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Whiteboard: [test which aborts the suite][closeme 2015-10-21] → [test which aborts the suite]
Assignee | ||
Updated•6 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•