Open
Bug 554772
Opened 15 years ago
Updated 2 years ago
2 reftest failures on sparc linux
Categories
(Core :: Layout, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: glandium, Unassigned)
Details
Attachments
(4 files)
I got 2 failures in reftests on sparc linux:
reftest> REFTEST TEST-UNEXPECTED-FAIL | file:///build/buildd-xulrunner_1.9.1.8-6-sparc-VDHGBV/xulrunner-1.9.1.8/layout/reftests/bugs/423385-1.html |
reftest> REFTEST TEST-UNEXPECTED-FAIL | file:///build/buildd-xulrunner_1.9.1.8-6-sparc-VDHGBV/xulrunner-1.9.1.8/layout/reftests/bugs/425247-2.html |
I'm attaching the corresponding png files. It appears the non -ref version has unexpected transparency set. What is strange, too, is that 425247-1.html doesn't fail.
I'll try to see if the failures are random or consistent.
If someone could point me at where in the code to look for something fishy, that would be appreciated.
Reporter | ||
Comment 1•15 years ago
|
||
Reporter | ||
Comment 2•15 years ago
|
||
Reporter | ||
Comment 3•15 years ago
|
||
Reporter | ||
Comment 4•15 years ago
|
||
I can't reproduce this failure "by hand" (i.e. connecting to a sparc machine and exporting a remote X display) :-/
I will try with the same environment as when we got the failure (with xvfb)
Reporter | ||
Comment 5•15 years ago
|
||
It unfortunately happens on random tests :(
On the other hand, considering comment 4 on bug 554774, this could be a problem with xvfb.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Reporter | ||
Comment 6•15 years ago
|
||
It appears that contrary to bug 554774, the problem is not on xvfb end. I can reproduce some reftest failures with a remote X display. The strange thing is that the failing reftests vary from time to time. Sometimes, failures start as soon as layout/reftests/reftest-sanity/test-async.html, sometimes a bit later, at layout/reftests/reftest-sanity/blank.html, and a lot more tests now fail than the origin 2 I gave. Though at the second try, only 3 were failing...
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•