[Debian-science-sagemath] Down to 190 failed tests

[François Bissey]

For the record this is the list of doctest failing in sage-on-gentoo:
----------------------------------------------------------------------
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/symbolic/expression.pyx  # 1 
doctest failed
sage -t --long /usr/lib64/python2.7/site-packages/sage/tests/cmdline.py 
# 1 doctest failed
sage -t --long /usr/lib64/python2.7/site-packages/sage/rings/integer.pyx 
  # 1 doctest failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/interfaces/singular.py  # 1 
doctest failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/repl/interpreter.py  # 3 
doctests failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/interfaces/tests.py  # 1 doctest 
failed
sage -t --long /usr/lib64/python2.7/site-packages/sage/numerical/mip.pyx 
  # 1 doctest failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/libs/glpk/error.pyx  # 1 doctest 
failed
sage -t --long /usr/lib64/python2.7/site-packages/sage/libs/libecm.pyx 
# 1 doctest failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/numerical/backends/glpk_backend.pyx 
  # 7 doctests failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/misc/gperftools.py  # 1 doctest 
failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/interfaces/qepcad.py  # 1 
doctest failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sagenb/notebook/misc.py  # 2 doctests 
failed
sage -t --long 
/usr/lib64/python2.7/site-packages/sage/numerical/backends/glpk_graph_backend.pyx 
  # 3 doctests failed
sage -t --long /usr/lib64/python2.7/site-packages/sage/ext/memory.pyx  # 
1 doctest failed
----------------------------------------------------------------------
I can make sage/symbolic/expression.pyx disappear as it is
https://github.com/pynac/pynac/issues/185
sage/rings/integer.pyx, sage/libs/libecm.pyx and sage/ext/memory.pyx
(and possibly sage/repl/interpreter.py) are due to using gmp instead
of mpir.
sage/numerical/backends/glpk_backend.pyx, sage/numerical/mip.pyx and
sage/numerical/backends/glpk_graph_backend.pyx are mismatch between
glpk used between vanilla sage and Gentoo.

Francois

On 03/10/16 11:51, Ximin Luo wrote:
> We are down to 190 failed tests.
>
> I fixed the ones from src/sage/groups/perm_gps/permgroup.py and src/sage/interfaces/gap.py which was happening due to cruft in my ~/.sage/gap folder. My patch is slightly hacky but it works; we might think about better solutions when doing the installation logic "properly", and then we should probably override DOT_SAGE or something.
>
> X
>
> Ximin Luo:
>> This is with the new python-cysignals-pari package, by Jerome. I also made some path fixes. Logs here:
>>
>> https://people.debian.org/~infinity0/res/sagemath-7.3+gitbab139c7+localparipatches+rebuiltlinbox_ptestlong.log
>> https://people.debian.org/~infinity0/res/sagemath-7.3+gitbab139c7+localparipatches+rebuiltlinbox_ptestlong.summary
>>
>> 10 tests containing the most failure cases:
>>
>> $ sort -k6n,6n logs/ptestlong.summary | tail -n10
>> sage -t --long src/sage/geometry/polyhedron/backend_cdd.py  # 7 doctests failed
>> sage -t --long src/sage/misc/sagedoc.py  # 7 doctests failed
>> sage -t --long src/sage/numerical/backends/glpk_backend.pyx  # 7 doctests failed
>> sage -t --long src/sage/numerical/optimize.py  # 7 doctests failed
>> sage -t --long src/sage/crypto/lwe.py  # 8 doctests failed
>> sage -t --long /usr/lib/python2.7/dist-packages/sagenb/notebook/notebook.py  # 8 doctests failed
>> sage -t --long src/sage/schemes/elliptic_curves/ell_rational_field.py  # 13 doctests failed
>> sage -t --long src/sage/symbolic/expression.pyx  # 15 doctests failed
>> sage -t --long src/sage/groups/perm_gps/permgroup.py  # 16 doctests failed
>> sage -t --long src/sage/interfaces/gap.py  # 57 doctests failed
>>
>> It looks like some of the tests are dependent on the docs being built - e.g. sagedoc.py from above.
>>
>> Unfortunately the docbuild (@master) now will segfault. I'm not sure why it didn't do that before; I will have to try `git bisect` at some point, or perhaps it was caused by Build-Dep updates. I've pushed a _wip_docbuild branch to fix the segfault, but now it keeps running out of memory - it didn't before, for one of my machines anyway. I will exit the rabbit hole for now...
>>
>> X
>>
>