I have tried running the matplotlib tests on MacOS 10.7 with Python 2.7 and Numpy 1.6.1, and am running into a number of failures. A fair fraction of the failures are test_axes failures: http://pastebin.com/MT2tBt8z
The matplotlib configuration was:
BUILDING MATPLOTLIB
matplotlib: 1.2.x
python: 2.7.2 (default, Feb 1 2012, 22:59:26) [GCC 4.2.1
Compatible Apple Clang 3.0
(tags/Apple/clang-211.12)]
platform: darwin
REQUIRED DEPENDENCIES
numpy: 1.6.1
freetype2: 14.0.8
OPTIONAL BACKEND DEPENDENCIES
libpng: 1.4.9
Tkinter: no
* TKAgg requires Tkinter
Gtk+: no
* Building for Gtk+ requires pygtk; you must be able
* to "import gtk" in your build/install environment
Mac OS X native: yes
Qt: no
Qt4: no
PySide: no
Cairo: no
OPTIONAL DATE/TIMEZONE DEPENDENCIES
datetime: present, version unknown
dateutil: matplotlib will provide
pytz: matplotlib will provide
adding pytz
OPTIONAL USETEX DEPENDENCIES
dvipng: no
ghostscript: /bin/sh: gs: command not found
latex: no
Activity
mdboom commented on Mar 20, 2012
Unfortunately, it's difficult to know what's going wrong here without the output images. We need to find a way to make sharing those easier...
astrofrog commented on Mar 20, 2012
I've uploaded the result_images directory after the tests to here: http://db.tt/e5AR8MAN - let me know if you need any other information!
astrofrog commented on Mar 20, 2012
It looks like the test_axes tests are failing because the axes frame is offset by 1 pixel in each dimension.
mdboom commented on Mar 20, 2012
Can you let me know if #779 addresses this for you?
jdh2358 commented on Mar 22, 2012
@astrofrog we need to close this before we cut the release candidate. Are these issues fixed now with the changes in #779
astrofrog commented on Mar 22, 2012
Yes, these tests are fixed with #779 with the new tests (the one with anti-aliasing disabled)