Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

[Russell O. <ro...@uw...>]

When I say "somehow missing" I'm not referring to the K (known fail). I'm referring to exceptions and tracebacks caused by trying to import test_X for various value of X: the modules were actually missing. I've never seen that before, so I was quite shocked. Normally I build on the oldest version of Mac OS X I can for the desired binary, but in this case I wanted to see what would happen if I built on 10.7 for a binary that works on 10.6 and 10.7. It resulted in this odd situation: the binary installed everything correctly on 10.7 but somehow failed to install some sub-packages on 10.6. Unfortunately I don't have time to look into it right now; I just took the simple way out of building again on 10.6. Unfortunately that meant a binary with known issues was up for a few hours. I do have the defective binary installer if anyone wants a look at it.

-- Russell

On Jul 5, 2012, at 12:47 PM, John Hunter wrote:

> 
> 
> On Thu, Jul 5, 2012 at 2:43 PM, Russell E. Owen <ro...@uw...> 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.
> 
> 
> Almost all of the test failures you ported were 'K' ie KNOWNFAIL.  Usually when you get a bunch of knownfails, it is because you don't have a prereq installed, eg inkscape for converting SVG.
> 
> Are you sure you have the requirements on all of the platforms
> 
> http://matplotlib.sourceforge.net/devel/coding_guide.html#requirements
> 
> Thanks,
> JDH