Dag Sverre Seljebotn wrote: > Michael Abshoff wrote: >> Dag Sverre Seljebotn wrote: >>> Stefan Behnel wrote: >>>> Robert Bradshaw wrote: >> <SNIP>
Hi Dag, >>> Sage passes doctests: Does that include detecting any leaks? The >>> refnanny is not yet working, so I'd be wary of releasing until that is >>> done unless we know that Sage doesn't leak more when Cython is upgraded. >> I don't think Robert did any testing, but I can do some valgrinding with >> the upcoming 3.3.alpha3 with the old and the new 0.11 snapshot to see if >> anything pops up. It will be a day or two until I have results. >> > > My refcount nanny now seems to be in a state where it doesn't crash > things (though there are spurious reports still from not following the > refnanny convention), and I've discovered at least one genuine leak so > far in the cython test suite. Excuse my ignorance, but how do I turn on the refnanny in all the code? I do not recall that being documented anywhere? I guess the best place might be the wiki for that. Did anybody fix that leak you mentioned above? > So in the event that you get lots of leaks, waiting for that to mature > may be a better angle. I have been distracted by other things, but I am about to start the valgrind run with the 0.10.3 to establish a baseline. This will take about 6 hours clock time if I use 12 to 18 CPUs at the same time. Once that is finished I will switch to the new Cython. I could also use another machine to do the second run in parallel, but some other users of the new Sage hardware might be less than happy about that :) Cheers, Michael _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
