On Mon, 2008-05-12 at 16:22 -0700, Glenn H Tarbox, PhD wrote:
> On Ubuntu 7.10 (hardy) x86_64 and i686 compilation and test ran to
> completion without problems.
ugh, got my numbers confused.
Everything ran to completion
- Ubuntu 8.04 (hardy) x86_64 and i686
- Ubuntu 7.10 (gutsy) x86_64
So, I
On Ubuntu 7.10 (hardy) x86_64 and i686 compilation and test ran to
completion without problems.
Running Gutsy x86_64 now and will report if there's trouble.
-glenn
On Mon, 2008-05-12 at 16:22 -0400, David Joyner wrote:
> On ubuntu 7.10amd64, install went fine but sage -testall failed with:
>
>
mabshoff wrote:
> On May 12, 9:45 pm, Alex Ghitza <[EMAIL PROTECTED]> wrote:
>
> Hi Alex,
>
>> Built and tested on three machines running Gentoo. One of them passed
>> without any glitches, but the other two got stuck at testdoc.py (the
>> same way as in 3.0.1).
>
> Did they time out eventuall
built (4 hours) and all tests passed (2 hours) on 32 bit arch linux,
using default make without any custom options
cheers,
Andrzej.
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
On ubuntu 7.10amd64, install went fine but sage -testall failed with:
--
The following tests failed:
sage -t devel/sage/sage/dsage/tests/testdoc.py
Total time for all tests: 10766.6 seconds
Here is what happened with
On May 12, 9:45 pm, Alex Ghitza <[EMAIL PROTECTED]> wrote:
Hi Alex,
> Built and tested on three machines running Gentoo. One of them passed
> without any glitches, but the other two got stuck at testdoc.py (the
> same way as in 3.0.1).
Did they time out eventually? Are you using pbuild?
> Bes
Built and tested on three machines running Gentoo. One of them passed
without any glitches, but the other two got stuck at testdoc.py (the
same way as in 3.0.1).
Best,
Alex
mabshoff wrote:
> Hello folks,
>
> this is Sage 3.0.2.alpha0. What happened? It seems that people
> were busy and unt
mabshoff wrote:
> Hello folks,
>
> this is Sage 3.0.2.alpha0. What happened? It seems that people
> were busy and until this morning there wasn't a whole lot to
> merge. But I had a busy day today and finally these is something
> to put out. We are still mostly on bug fix only mode, so no big
> s
