I did a git checkout of the v1.1.1 tag and compiled a 64-bit version. I
have attached output from the following command:
python -c "import matplotlib as m ; m.test(verbosity=1)"
Note that some of the tests fail with satuses: KEFKK.
I have the following requirements installed:
nose: version 1.1.2
PIL: version 1.1.7
ghsotscript: version 9.05
inkscape: 0.48.3.1
All of these were installed using the latest version of macports.
Is there anything I can do to improve the output of the tests?
test_output.txt (4.11 KB)
···
On Thu, Jul 05, 2012 at 07:43:39PM +0000, Russell E. Owen wrote:
In article <EF3F693B-B19F-4CF2-9416-F073203B3A26@...748...>,
Russell Owen <rowen@...748...> wrote:
> I just uploaded the Mac binaries.
>
> Several minor concerns:
> - Many unit tests failed on Mac OS X 10.4 (which is where I build the 10.3.9
> version) due to "too many files open", but the same binary looks fine on
> 10.5.
> - The 64-bit version (10.6 and later) had one unexpected failure on 10.7 (I
> have not yet had time to test it on 10.6)...
When I tested on Mac OS X 10.6 I found that most unit tests were somehow
missing. Rather than try to diagnose the problem, I built a new binary
on 10.6, confirmed that it installed properly (with all unit tests) on
10.6 and 10.7, then uploaded it to replace the earlier 10.6 binary.
The same test I mentioned in my previous post still fails using the new
binary, on both 10.6 and 10.7.
-- Russell
--
Damon McDougall
http://damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom
I see the same 3 known failures building with fink and the same versions of the above
dependencies, and also get the already mentioned Stix failure. Everything else succeeds
on 10.5, but I get a different inkscape error on 10.7:
···
On 06.07.2012, at 3:49PM, Damon McDougall wrote:
When I tested on Mac OS X 10.6 I found that most unit tests were somehow
missing. Rather than try to diagnose the problem, I built a new binary
on 10.6, confirmed that it installed properly (with all unit tests) on
10.6 and 10.7, then uploaded it to replace the earlier 10.6 binary.
The same test I mentioned in my previous post still fails using the new
binary, on both 10.6 and 10.7.
-- Russell
I did a git checkout of the v1.1.1 tag and compiled a 64-bit version. I
have attached output from the following command:
python -c "import matplotlib as m ; m.test(verbosity=1)"
Note that some of the tests fail with satuses: KEFKK.
I have the following requirements installed:
nose: version 1.1.2
PIL: version 1.1.7
ghsotscript: version 9.05
inkscape: 0.48.3.1
All of these were installed using the latest version of macports.
Is there anything I can do to improve the output of the tests?
+++++
IOError: Conversion command failed:
inkscape -z /scratch.noindex/fink.build/matplotlib-py27-1.1.1-1/matplotlib-1.1.1/result_images/test_legend/legend_auto2.svg --export-png /scratch.noindex/fink.build/matplotlib-py27-1.1.1-1/matplotlib-1.1.1/result_images/test_legend/legend_auto2_svg.png
Standard output:
Background RRGGBBAA: ffffff00
Area 0:0:720:540 exported to 720 x 540 pixels (90 dpi)
Bitmap saved as: /scratch.noindex/fink.build/matplotlib-py27-1.1.1-1/matplotlib-1.1.1/result_images/test_legend/legend_auto2_svg.png
Standard error:
(inkscape:25527): libgnomevfs-WARNING **: Unable to create ~/.gnome2 directory: Permission denied
File display/nr-arena-item.cpp line 147 (?): Assertion child->parent == NULL failed
**
ERROR:sp-clippath.cpp:308:void sp_clippath_hide(SPClipPath*, unsigned int): code should not be reached
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
** Message: Error: Inkscape encountered an internal error and will close now.
+++++
This is obviously an inscape bug to be reported it to its respective maintainers.
I found that on the Inkscape web site 0.48.2 is advertised as the stable release,
so I tried downgrading to that version, but just get a similar crash on a different file.
Cheers,
Derek