Bug 47974 - Tests fail
Summary: Tests fail
Status: RESOLVED MOVED
Alias: None
Product: cairo
Classification: Unclassified
Component: quartz backend (show other bugs)
Version: 1.12.0
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: Vladimir Vukicevic
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-27 19:07 UTC by Ryan Schmidt
Modified: 2018-08-25 13:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
log (782.31 KB, application/x-bzip2)
2012-03-27 19:07 UTC, Ryan Schmidt
Details

Description Ryan Schmidt 2012-03-27 19:07:23 UTC
Created attachment 59134 [details]
log

The test suite ends with "1 of 1 test failed" asking me to report the bug here. But there are many previous lines where it says tests failed or crashed. I'm attaching the MacPorts build and test log; it's 150MB when decompressed. Not sure what other information you require. This was on OS X 10.6.8 with Xcode 3.2.6 on a 64-bit MacBook Pro with a 2.2-GHz Core 2 Duo CPU.
Comment 1 Ryan Schmidt 2012-03-27 19:10:45 UTC
I should add that after the test suite ended, an "any2ppm" process was left running consuming one CPU until I killed it.
Comment 2 snc 2012-05-18 11:54:40 UTC
I'm also seeing this problem using 10.7 on a 2.8GHz Core 2 Duo.

When I compile PSPP against cairo, it will build however PSPP's own tests fail because cairo's issues. Using PSPP is then perilous. This applies to just about anything making use of Cairo—anything GTK comes to mind.

If you need access to an environment for testing, please let me know.
Comment 3 GitLab Migration User 2018-08-25 13:52:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/cairo/cairo/issues/237.


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.