a8-mask-image: XFAIL a8-mask-xlib: XFAIL XFAIL: a8-mask caps-sub-paths-xlib: FAIL FAIL: caps-sub-paths clip-nesting-xlib: FAIL FAIL: clip-nesting clip-operator-xlib: FAIL FAIL: clip-operator clip-twice-xlib: FAIL FAIL: clip-twice dash-offset-negative-xlib: FAIL FAIL: dash-offset-negative fill-and-stroke-xlib: FAIL FAIL: fill-and-stroke fill-rule-xlib: FAIL FAIL: fill-rule filter-nearest-offset is expected to fail: wrong sampling location for nearest-neighbor filter in libpixman and Render filter-nearest-offset-image: XFAIL filter-nearest-offset-xlib: XFAIL XFAIL: filter-nearest-offset leaky-polygon-xlib: FAIL FAIL: leaky-polygon line-width-xlib: FAIL FAIL: line-width mask-xlib: FAIL FAIL: mask operator-source-xlib: FAIL FAIL: operator-source path-data-xlib: FAIL FAIL: path-data pixman-rotate is expected to fail: known off-by-one bug when rotating a pixman image pixman-rotate-image: XFAIL pixman-rotate-xlib: XFAIL XFAIL: pixman-rotate self-copy-xlib: FAIL FAIL: self-copy self-intersecting is expected to fail: Self-intersecting strokes are wrong due to incremental trapezoidization.self-intersecting-image: XFAIL self-intersecting-xlib: XFAIL XFAIL: self-intersecting show-text-current-point-xlib: FAIL FAIL: show-text-current-point text-antialias-gray-xlib: FAIL FAIL: text-antialias-gray text-antialias-subpixel-xlib: FAIL FAIL: text-antialias-subpixel text-rotate is expected to fail: minor bugs in positioning rotated glyphs text-rotate-image: XFAIL text-rotate-xlib: XFAIL XFAIL: text-rotate transforms-xlib: FAIL FAIL: transforms trap-clip-xlib: FAIL FAIL: trap-clip unantialiased-shapes-xlib: FAIL FAIL: unantialiased-shapes rel-path-xlib: FAIL FAIL: rel-path
Hmm, odd to have complete failure like that. Either suggests something was very broken in that release of the test suite, or the environment, or both. Closing due to its age and the number of radical changes since. Please try the current stable version, 1.8.0, and tell us if you find any problems - thanks!
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.