Bug 6298 - 23 of 60 tests FAIL, all for xlib backend
Summary: 23 of 60 tests FAIL, all for xlib backend
Status: RESOLVED NOTABUG
Alias: None
Product: cairo
Classification: Unclassified
Component: xlib backend (show other bugs)
Version: 1.0.2
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-17 20:52 UTC by Peter Breitenlohner
Modified: 2006-03-22 12:31 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Peter Breitenlohner 2006-03-17 20:52:47 UTC
When running "make check" 23 of 60 tests FAIL for cairo-1.0.2 and the same 23
tests (out of 61) FAIL for cairo-1.0.4. All failures are due to the xlib backend:

caps-joins-xlib, caps-sub-paths-xlib, clip-nesting-xlib, clip-operator-xlib,
clip-twice-xlib, composite-integer-translate-over-xlib, dash-caps-joins-xlib,
dash-offset-negative-xlib, fill-and-stroke-xlib, fill-rule-xlib,
leaky-polygon-xlib, line-width-xlib, linear-gradient-xlib, mask-xlib,
operator-clear-xlib, operator-source-xlib, path-data-xlib,
rectangle-rounding-error-xlib, transforms-xlib, trap-clip-xlib,
unantialiased-shapes-xlib, unbounded-operator-xlib, and rel-path-xlib.

Could these failure be due to a somewhat oldish libX11 (Xfree86-4.4.0)
Comment 1 Owen Taylor 2006-03-18 00:18:36 UTC
Yes
Comment 2 Carl Worth 2006-03-23 07:31:20 UTC
Here's the explanatory note for this currently hiding up in cairo/INSTALL for
some reason:

   NOTE: Some versions of X servers will cause the -xlib tests to
   report failures in make check even when cairo is working just
   fine. If you see failures in nothing but -xlib tests, please
   examine the corresponding -xlib-out.png images and compare them to
   the -ref.png reference images (the -xlib-diff.png images might also
   be useful). If the results seem "close enough" please do not report
   a bug against cairo as the "failures" you are seeing are just due
   to subtle variations in X server implementations.

This note should probably be put into test/README and perhaps included in the
output of a "make check" failure, (particularly if we could convince make check
to notice when only xlib-specific tests fail).


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.