Re: [matplotlib-devel] mpl release candidate branch

[John H. <jd...@gm...>]

On Sat, Sep 24, 2011 at 12:37 AM, Benjamin Root <ben...@ou...> wrote:
> Working through the checklist, I am wary of cutting an RC at this particular
> moment.  Why is just about a quarter of all the tests coming back as known

There are only two legit known fails, one in test_basic and one in
test_dates and these are the only two I am seeing.  You are likely
seeing known fails on the pdf or svg tests because either you don't
have gs or inkscape installed to do the image conversion.  Take a look
at ib/matplotlib/testing/compare.py to see the conversion commands

> fails?  Also, running unit/memleak_hawaii3.py is showing what seems to be a
> memory leak (GTKAgg, Python 2.7, Ubuntu, 32-bit) on my system.  The step ups
> are about 40-50 KB at about once every 10 seconds.

I can't test this now because I am leaving for a roadtrip now until
tomorrow night; usually this steps up a bit on initial figures and
then stabilizes after a large number of figures.  I don't have a
problem waiting til Monday to sort out a few lingering issues.  I also
don't have a problem branching and cutting the rc now because we can
always fix things in the branch, but this increases the workload
because of the additional merge.  So why don't we keep hammering on
the few remaining issues and shoot for Monday afternoon?