FWIW, on Debian testing running on core i5 + 8 GB RAM, ptestalllong gets similar results :
- No permanent failure (yay !) - Eleven transient failures, all already seen in previous 9.x betas : File | Result ----------------------------------------------+------------------- src/sage/combinat/posets/posets.py | 1 doctest failed src/sage/plot/animate.py | 7 doctests failed src/sage/combinat/matrices/hadamard_matrix.py | 2 doctests failed src/sage/misc/latex.py | 1 doctest failed src/sage/misc/persist.pyx | 2 doctests failed src/sage/coding/databases.py | 2 doctests failed src/sage/repl/load.py | 1 doctest failed src/sage/graphs/graph_latex.py | 2 doctests failed src/sage/misc/remote_file.py | 2 doctests failed src/sage/databases/findstat.py | 72 doctests failed src/sage/interfaces/magma_free.py | 2 doctests failed As far as I can, tell, I never saw these failures when doing testlong. It looks more and more like a problem of concurrency specific to ptestalllong, unrelated to Python3. Is this ticket-worthy ? Le mercredi 6 novembre 2019 10:19:10 UTC+1, Eric Gourgoulhon a écrit : > > On Ubuntu 18.04 running on a bi-Xeon E5-2623 (8 cores) + 16 GB RAM > computer and for a *python3 *build: > > - incremental build (from 9.0.beta3, with -j16) OK > - all tests from ptestlong passed > > This is the first time that Python-3 Sage passes all the tests on this > computer! (thanks to the inclusion of #28334 and #28622 in this release). > > Eric. > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/debfdc0d-5c76-41bb-864d-b839025a88ab%40googlegroups.com.
