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.
sage -t "devel/sage/sage/schemes/elliptic_curves/heegner.py" # Segfault
sage -t "devel/sage/sage/plot/plot.py" # Segfault
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
sage -t "devel/sage/sage/rings/polynomial/symmetric_ideal.py" #
Segfault
Total time for all tests: 28172.6 seconds
I'm wondering if the timeout might be too short for this rather old machine
(about 10 years old).
Full log at:
http://boxen.math.washington.edu/home/kirkby/doctest-results/1/
Comments?
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
