clip-nesting-xlib: FAIL FAIL: clip-nesting clip-operator-xlib: FAIL FAIL: clip-operator clip-twice-xlib: FAIL FAIL: clip-twice composite-integer-translate-over-xlib: FAIL FAIL: composite-integer-translate-over fill-and-stroke-xlib: FAIL FAIL: fill-and-stroke fill-rule-xlib: FAIL FAIL: fill-rule leaky-polygon-xlib: FAIL FAIL: leaky-polygon line-width-xlib: FAIL FAIL: line-width mask-xlib: FAIL FAIL: mask paint-with-alpha-xlib: FAIL FAIL: paint-with-alpha path-data-xlib: FAIL FAIL: path-data scale-source-surface-paint-xlib: FAIL FAIL: scale-source-surface-paint text-antialias-gray-xlib: FAIL FAIL: text-antialias-gray transforms-xlib: FAIL FAIL: transforms trap-clip-xlib: FAIL FAIL: trap-clip unantialiased-shapes-xlib: FAIL FAIL: unantialiased-shapes unbounded-operator-xlib: FAIL FAIL: unbounded-operator rel-path-xlib: FAIL FAIL: rel-path
The Xlib tests aren't 100% useful in their current form for a couple of reasons: 1) The tests currently test for bit-for-bit accuracy, which is likely more than we really want to demand from X servers. 2) Various X server versions have various rendering bugs. These often lead to failures in the test suite, (even if the results are "good enough"). I suggest comparing the test/*-xlib-out.png and test/*-ref.png images to see if the results look "good enough" to you.
Move bugs against "cvs" version to "0.9.3" so we can remove the "cvs" version.
Tests currently check for pixel-perfectness :(
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.