Hello folks,

I raised the issue with optional doctest failures in Sage 3.2.a0 a
while back and I am glad to report that we have made some progress
here:

        sage -t -long -optional devel/sage/sage/tests/benchmark.py # 4
doctests failed
        sage -t -long -optional devel/sage/sage/rings/polynomial/
term_order.py # 1 doctests failed
        sage -t -long -optional devel/sage/sage/rings/polynomial/
polynomial_element_generic.py # 1 doctests failed
        sage -t -long -optional devel/sage/sage/rings/polynomial/
pbori.pyx # 2 doctests failed
        sage -t -long -optional devel/sage/sage/rings/polynomial/
multi_polynomial_ring.py # 2 doctests failed
        sage -t -long -optional devel/sage/sage/rings/polynomial/
multi_polynomial_ideal.py # 5 doctests failed
        sage -t -long -optional devel/sage/sage/rings/
fraction_field_element.py # 2 doctests failed
        sage -t -long -optional devel/sage/sage/modules/free_module.py
# 1 doctests failed
        sage -t -long -optional devel/sage/sage/modular/ssmod/ssmod.py
# 1 doctests failed
        sage -t -long -optional devel/sage/sage/schemes/
elliptic_curves/sha_tate.py # 1 doctests failed
        sage -t -long -optional devel/sage/sage/schemes/
elliptic_curves/ell_rational_field.py # 1 doctests failed
        sage -t -long -optional devel/sage/sage/matrix/matrix1.pyx # 2
doctests failed
        sage -t -long -optional devel/sage/sage/libs/pari/gen.pxi # 1
doctests failed
        sage -t -long -optional devel/sage/sage/libs/pari/gen.pyx # 1
doctests failed
        sage -t -long -optional devel/sage/sage/interfaces/r.py # 10
doctests failed
        sage -t -long -optional devel/sage/sage/interfaces/mupad.py #
67 doctests failed
        sage -t -long -optional devel/sage/sage/interfaces/magma.py #
2 doctests failed
        sage -t -long -optional devel/sage/sage/interfaces/maple.py #
1 doctests failed
        sage -t -long -optional devel/sage/sage/interfaces/lie.py # 1
doctests failed
        sage -t -long -optional devel/sage/sage/interfaces/
mathematica.py # 17 doctests failed
        sage -t -long -optional devel/sage/sage/graphs/
graph_database.py # 1 doctests failed
        sage -t -long -optional devel/sage/sage/geometry/polytope.py #
7 doctests failed
        sage -t -long -optional devel/sage/sage/functions/constants.py
# 1 doctests failed
        sage -t -long -optional devel/sage/sage/databases/jones.py # 2
doctests failed
        sage -t -long -optional devel/sage/sage/databases/sloane.py #
1 doctests failed
        sage -t -long -optional devel/sage/sage/crypto/mq/
mpolynomialsystem.py # 1 doctests failed
        sage -t -long -optional devel/sage/sage/combinat/species/
library.py # 4 doctests failed
        sage -t -long -optional devel/sage/sage/combinat/crystals/
crystals.py # 2 doctests failed
        sage -t -long -optional devel/sage/sage/combinat/
sloane_functions.py # 1 doctests failed
        sage -t -long -optional devel/sage/sage/calculus/calculus.py #
1 doctests failed

Note that at least two of those above tests will likely pass when I
have MuPAD and polymake installed. The sage/interfaces/magma.p failure
is due to bugs in Magma 2.13 installed on the system while 2.14 does
pass doctests. There are also some failures due to missing dot2tex and
also some missing db packages it seems. Once I am back in Germany I
will post a script that installs all the components automatically to
make it easier on sage.math to install all this goodness.

In case you care about one of the above doctests check out the log at

  
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/3.2.rc0-testall-long-optional.txt

It is about 300kb. Quite a number of the above issues already do have
tickets.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to