2012/1/15 Robert Bradshaw :
> 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 hom
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
On Sat, Jan 14, 2012 at 9:38 AM, Robert Bradshaw
wrote:
> On Sat, Jan 14, 2012 at 6:19 AM, Vitja Makarov
> wrote:
>> I've r
On Sat, Jan 14, 2012 at 6:19 AM, Vitja Makarov 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
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?
--
vitja.
___
cython-devel mailing list
c
