2012/1/15 Robert Bradshaw <rober...@math.washington.edu>: > OK, thinks are looking a lot better, but there's still quite a few > random segfaults: > > https://sage.math.washington.edu:8091/hudson/view/ext-libs/job/sage-tests/674/console >
Cool. Have you modified a private copy of sage? I've tried to reproduce segfaults at home but I was unable to compile sage due to incompatible changes in cython. > On Sat, Jan 14, 2012 at 9:38 AM, Robert Bradshaw > <rober...@math.washington.edu> wrote: >> On Sat, Jan 14, 2012 at 6:19 AM, Vitja Makarov <vitja.maka...@gmail.com> >> wrote: >>> I've recently merged my def-node-refactoring branch and found some >>> bugs, thanks to sage-build. >>> >>> Then I've found that sage-tests has >100 failures. >>> So I'm wondering does anybody know what's wrong with sage-tests? >> >> Yeah, sage-tests is a great stress-tester for Cython. There were a >> couple of spurious failures before, but nothing this bad. >> >> I blame >> https://github.com/cython/cython/commit/bce8b981a3e71378a164e8c9acca5f00bbbe32d7 >> which is causing variables to be undefined. Arguably, this is a bug in >> Sage, but it was a backwards incompatible change. >> >> - Robert > _______________________________________________ > cython-devel mailing list > cython-devel@python.org > http://mail.python.org/mailman/listinfo/cython-devel -- vitja. _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
