Dr. David Kirkby wrote:
I thought I'd report the doctests results on Solaris. I know Solaris has
never passed them all, but the number of failures is not very large now
I've implemented something much faster to get the memory usage, which
was screwing up some tests.
There are 10 failures. The first two are failures are numerical noise
issues, which are awaiting review at
http://trac.sagemath.org/sage_trac/ticket/8374
http://trac.sagemath.org/sage_trac/ticket/8375
(someone please get these easy ones out of the way.)
That still leaves 8 failures.
After increasing the timeout, 3 more of the tests passed, so my poor 10-year old
SPARC is not fast enough! I reckon on 't2', the SAGE_TIMEOUT should be increased
to about 1800 s to be sure there are no spurious timeout errors, as
sage -t "devel/sage/sage/schemes/elliptic_curves/heegner.py"
[440.9 s]
sage -t "devel/sage/sage/plot/plot.py"
[422.8 s]
sage -t "devel/sage/sage/rings/polynomial/symmetric_ideal.py"
[459.4 s]
So that leaves just 5 unexplained failures on Solaris
sage -t "devel/sage/sage/graphs/graph_list.py" # Segfault
sage -t "devel/sage/sage/graphs/generic_graph.py" # Segfault
sage -t "devel/sage/sage/graphs/graph.py" # Segfault
sage -t "devel/sage/sage/graphs/graph_database.py" # Segfault
sage -t "devel/sage/sage/databases/database.py" # Segfault
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
