Michel <[EMAIL PROTECTED]> writes:
> I can confirm that this particular test *sometimes* fails for me also.
Does it always fail the same way? With the same output, on both
machines?
Nick
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@goog
On 6/19/07, Michel <[EMAIL PROTECTED]> wrote:
>
> William,
>
> A while ago I reported that the implementation of
>
> RR(0).exact_rational()
>
> made some machines run out of memory, giving weird
> doctest errors.
>
> You posted a patch (special casing zero) but I now see
> in the source of sage-2.
I can confirm that this seems to be what is going on. Usually, when I
run
./sage -t devel/sage-main/sage/rings/real_mpfr.pyx
all of my memory gets eaten up. It worked just fine once, but never
again. And I just tried
RR(0).exact_rational()
which causes the same problems.
On Tue, 2007-06-19
William,
A while ago I reported that the implementation of
RR(0).exact_rational()
made some machines run out of memory, giving weird
doctest errors.
You posted a patch (special casing zero) but I now see
in the source of sage-2.6 you forgot to apply it.
Can you please apply!
Regards,
Michel
I can confirm that this particular test *sometimes* fails for me also.
I also don't know what the cause is.
Here is my /proc/cpuinfo.
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : AMD Athlon(tm) XP 2200+
stepping: 1
cpu MHz
