On Mar 30, 6:31 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> rc0 -- On every single test machine
> sage -t devel/sage-main/sage/dsage/tests/testdoc.py
> fails.
Yeah, but as Yi wrote below it is an exception thrown at exit. I don't
consider it a show stopper for 2.10.4.
> On Meccah (athlon 32-bit):
>
> sage -t devel/sage-main/sage/interfaces/psage.py
> sage -t devel/sage-main/sage/interfaces/sage0.py
> sage -t devel/sage-main/sage/misc/functional.py
> sage -t devel/sage-main/sage/dsage/tests/testdoc.py
> sage -t devel/sage-main/sage/rings/quotient_ring.py
> sage -t devel/sage-main/sage/calculus/calculus.py
>
> Total time for all tests: 17848.8 seconds
The box is heavily pushed into swap:
Mem: 1036040k total, 1030384k used, 5656k free, 4188k
buffers
Swap: 2048248k total, 1440436k used, 607812k free, 6536k
cached
So I think that is it likely that Sage + second Sage instance or Sage
+ maxima for example exhausts the physically available memory.
According to the log Maxima crashed at least once. So I would also
discount theses error reports until the tests are rerun on a box that
isn't so heavily pushed. By the way: the only offending process
consuming 78.5% of the memory is the one below:
17820 XXX 15 0 1003m 794m 3568 D 1.3 78.5 1272:40 python2.4
And that seems to be a rather leaky process or accounting on that box
is FUBAR.
> See /home/was/build/tests/meccah.log for the log.
>
> William
What does concern me are David's failure, but unless somebody gets
access on his box to debug or is able to reproduce them locally I see
little hope to get this fixed for 2.11. So from my end: Let's push the
button.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
