After rebuilding after "make distclean" on the first machine (but without 
reinstallation of optional packages), "ptestalllong" gets me results close 
to those reported 
<https://groups.google.com/d/msg/sage-release/JufDVoygjw8/wH-TTTinAAAJ> for 
8.9.rc0, albeit with a slightly shorter list of transient failures:

src/sage/plot/animate.py                     
src/sage/combinat/matrices/hadamard_matrix.py
src/sage/misc/latex.py                       
src/sage/misc/persist.pyx                    
src/sage/coding/databases.py                 
src/sage/repl/load.py                        
src/sage/databases/findstat.py               
src/sage/misc/remote_file.py                 
src/sage/combinat/designs/ext_rep.py         
src/sage/interfaces/magma_free.py            
src/sage/interfaces/mathematica.py           

Sorry for the noise... HTH,



Le mercredi 25 septembre 2019 14:45:00 UTC+2, Emmanuel Charpentier a écrit :
>
> Hmmm... This one is nasty...
>
> On Debian testing running on core i5 + 8 GB RAM, upgrading from 8.9.rc0, I 
> get:
>
> Transient errors:
>
>   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/databases/findstat.py                   9 doctests failed
>   src/sage/misc/remote~file~.py                    2 doctests failed
>   src/sage/combinat/designs/ext~rep~.py            1 doctest failed
>   src/sage/interfaces/magma~free~.py               2 doctests failed
>   src/sage/interfaces/mathematica.py               Timed out
>
> Permanent errors, already known:
>
>   src/sage/libs/eclib/interface.py                          1 doctest 
> failed
>   src/sage/rings/polynomial/polynomial~rationalflint~.pyx   1 doctest 
> failed
>
> New permanent errors due to aborts:
>
>   src/sage/crypto/mq/sr.py                                   Killed due to 
> abort
>   src/sage/rings/polynomial/multi~polynomialsequence~.py     Killed due to 
> abort
>   src/sage/rings/polynomial/pbori.pyx                        Killed due to 
> abort
>   src/sage/rings/polynomial/polynomial~ringconstructor~.py   Killed due to 
> abort
>   src/sage/sat/solvers/dimacs.py                             Killed due to 
> abort
>   src/doc/en/reference/sat/index.rst                         Killed due to 
> abort
>   src/sage/sat/boolean~polynomials~.py                       Killed due to 
> abort
>
> Details in SageTstAborts (attached).
>
> Looking at those details, in all but one case, the abort is a "length 
> error":
>
>   src/sage/crypto/mq/sr.py                                   terminate 
> called after throwing an instance of \'std::length~error~\'
>   src/sage/rings/polynomial/multi~polynomialsequence~.py     terminate 
> called after throwing an instance of \'std::length~error~\'
>   src/sage/rings/polynomial/pbori.pyx                        terminate 
> called after throwing an instance of \'std::bad~alloc~\'
>                                                              terminate 
> called recursively
>   src/sage/rings/polynomial/polynomial~ringconstructor~.py   terminate 
> called after throwing an instance of \'std::length~error~\'
>   src/sage/sat/solvers/dimacs.py                             terminate 
> called after throwing an instance of \'std::length~error~\'
>   src/doc/en/reference/sat/index.rst                         terminate 
> called after throwing an instance of \'std::length~error~\'
>   src/sage/sat/boolean~polynomials~.py                       terminate 
> called after throwing an instance of \'std::length~error~\'
>
>
> The exception in pbori.pyx, seems to be multiple errors.
>
> I suppose tat something may be broken in my setup. Hints about how to 
> unhose my system are welcome...
>
> HTH,
>
>
>
> Le mercredi 25 septembre 2019 01:15:52 UTC+2, Volker Braun a écrit :
>>
>> As always, you can get the latest beta version from the "develop" git 
>> branch. Alternatively, the self-contained source tarball is at 
>> http://www.sagemath.org/download-latest.html 
>>
>> 2ab843c20b (trac/develop, tag: 8.9.rc1) Updated SageMath version to 
>> 8.9.rc1
>> 26677b4e26 Trac #25026: Update jmol to version 14.29.52
>> 582a9ef4fd Trac #28444: Fix backwards incompatibility of unpickling in 
>> Python 3
>> 2eff516090 Trac #28059: Some citations are missing from pdf docs
>> be66263728 (tag: 8.9.rc0) Updated SageMath version to 8.9.rc0
>>
>>

-- 
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 sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/502444c5-0e17-41c7-b346-65f526615dd8%40googlegroups.com.

Reply via email to