On 10 Sep., 22:33, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 10, 9:51 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>
> > Hi,
>
> Him
>
> > I'm not sure what has been reported so far regarding building rc1, but here
> > are some failures.
>
> > On OSX 10.5 these fail:
>
> > sage -t -long devel/sage/sage/crypto/mq/sr.py
>
> Memory
>
> > sage -t -long devel/sage/sage/interfaces/lisp.py
>
> This is a new one, but I have seen it also on varro
>
> > sage -t -long devel/sage/sage/matrix/matrix_real_double_dense.pyx
>
> #4091
>
> > sage -t -long
> > devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py
>
> Memory
>
> > sage -t -long
> > devel/sage/sage/schemes/elliptic_curves/period_lattice.py
>
> Numerical noise - likely fixed in rc2 by #4093
>
> > On sage.math this fails:
>
> > sage -t -long devel/sage/sage/interfaces/maxima.py
>
> I cannot reproduce this.
>
> > On my 32-bit debian test vmware image these all fail:
>
> > sage -t -long devel/sage/sage/matrix/matrix_real_double_dense.pyx
>
> #4091
>
> > sage -t -long devel/sage/sage/stats/hmm/hmm.pyx
> > sage -t -long devel/sage/sage/stats/hmm/chmm.pyx
>
> numerical noise: #3978
>
> > sage -t -long devel/sage/sage/dsage/dist_functions/dist_factor.py
>
> no clue
>
> > sage -t -long
> > devel/sage/sage/schemes/elliptic_curves/period_lattice.py
>
> #4093
>
> > sage -t -long devel/sage/sage/crypto/mq/sr.py
>
> Lack of memory
>
> > On the 64-bit image only the sr.py one fails (lack of memory).
>
> > On arch linux these two fail:
>
> > sage -t -long devel/sage/sage/crypto/mq/sr.py
> > sage -t -long devel/sage/sage/interfaces/psage.py
>
> Memory?
>
> > On OSX 10.5 ppc (Clement Pernet's office computer), the doctests
> > hang here forever (for at least one day):
>
Hi,
> > sage -t -long devel/sage/sage/interfaces/lisp.py
>
> > (hangs forever)
>
> Yeah, I had to kill that one, too. After that all the other tests went
> on and there we some failures.
I want to add this potential explanation:
The basic problem seems to be low memory, making Maxima crash. But the
"automatic restarting", which in most of the cases gives an error
message containing "Maxima crashed -- automatically restarting." (and
then the test suite continues), seems to fail sporadically (memory
sometimes not being freed "fast enough"?!).
Experimenting with low memory giving those failures with "Maxima
crashed -- automatically restarting.",
I saw several runs of "piecewise.py" which failed with error message,
and then continued. But on one run of that "piecewise.py":
...
sage -t -long devel/sage/sage/functions/piecewise.py ^Cmake:
*** [testlong] Error 130
the test suite did just hang (almost no CPU load visible, the lisp.run
tasks were idle, as well as the python task).
After hitting "Control-C", lisp.run task drew CPU time again, and
eventually make failed gracefully (if "Error 130" could be called
thus.)
Cheers,
gsw
>
> > Only this fails on iras/itanium:
>
> > sage -t -long devel/sage/sage/matrix/matrix_real_double_dense.pyx
>
> #4093
>
> > sage -t -long devel/sage/sage/stats/hmm/chmm.pyx
> > sage -t -long devel/sage/sage/stats/hmm/hmm.pyx
>
> both #3984
>
> 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
-~----------~----~----~----~------~----~------~--~---
