[sage-release] Re: Sage 8.9.rc1 released

2019-09-26 Thread Emmanuel Charpentier
After rebuilding after "make distclean" on the first machine (but without 
reinstallation of optional packages), "ptestalllong" gets me results close 
to those reported 
 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.pyx2 doctests failed
>   src/sage/coding/databases.py 2 doctests failed
>   src/sage/repl/load.py1 doctest failed
>   src/sage/graphs/graph~latex~.py  2 doctests failed
>   src/sage/databases/findstat.py   9 doctests failed
>   src/sage/misc/remote~file~.py2 doctests failed
>   src/sage/combinat/designs/ext~rep~.py1 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.pyxKilled 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.pyxterminate 
> 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, 

Re: [sage-release] Re: Sage 8.9.rc1 released

2019-09-26 Thread Samuel Lelièvre
Thu 2019-09-26 06:21 UTC, Markus Wageringel:
>
> With Python 2, I got a (transient) timeout in
>
> src/sage/parallel/map_reduce.py
>
> There seems to be a race condition. It is difficult for me to reproduce.
> Has anyone seen this before?

Yes, it comes up once in a while. See previous mentions in sage-release:

https://groups.google.com/forum/#!searchin/sage-release/map_reduce%7Csort:date

and occasionally on sage-devel:

https://groups.google.com/forum/#!searchin/sage-devel/map_reduce%7Csort:date

> I am unsure whether this might have been caused by the recent changes
> to RecursivelyEnumeratedSet in #27967.

-- 
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/CAEcArF1BWorMT6z5LybTJvc2h1-5KCNxCs5YfwpaByzaein2qw%40mail.gmail.com.


[sage-release] Re: Sage 8.9.rc1 released

2019-09-26 Thread Sébastien Labbé

>
> I am unsure whether this might have been caused by the recent changes to 
> RecursivelyEnumeratedSet in #27967.
>

I don't think so as the changes in #27967 are not related to the search 
forest (and map_reduce.py) code.
 

-- 
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/32fc1a35-50c1-481c-8313-12158977edd5%40googlegroups.com.


[sage-release] Re: Sage 8.9.rc1 released

2019-09-26 Thread Markus Wageringel
With Python 3 on CentOS, all tests from ptestlong passed.

With Python 2, I got a (transient) timeout in

src/sage/parallel/map_reduce.py

There seems to be a race condition. It is difficult for me to reproduce. 
Has anyone seen this before? I am unsure whether this might have been 
caused by the recent changes to RecursivelyEnumeratedSet in #27967.

-- 
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/a8f32d79-32d0-4bf5-bc5a-baf12b107fe6%40googlegroups.com.


[sage-release] Re: Sage 8.9.rc1 released

2019-09-25 Thread Emmanuel Charpentier
On the second machine, upgrading a Python 3-based Sage to 8.9.rc1, adding 
Trac#28524  and ptestalllong'ing it 
gives the same failures as previously reported 
 for 
8.9.rc0, i. e. permanent failures for eclib/interface, Flint, and 
gap_packages. No killed tests.

My tentative conclusion is that I may have inadvertently hosed the first 
machine's Sage installation. Will rebuild it from scratch and report the 
results (but not for the next day...).

HTH,

Le mercredi 25 septembre 2019 16:03:12 UTC+2, Emmanuel Charpentier a écrit :
>
> Forgot to specify that these results were for ptestalllong, which is now 
> pertinent for Python 3-based Sage...
>
> Incidentally, testing on another machine a patch for ticket Trac#28534 
>  (which needed a large 
> recompilation), ptest-python3 gives only the well-known failure related 
> to FLINT. Currently running ptestalllong on this other machine.
>
> 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.pyx2 doctests failed
>>   src/sage/coding/databases.py 2 doctests failed
>>   src/sage/repl/load.py1 doctest failed
>>   src/sage/graphs/graph~latex~.py  2 doctests failed
>>   src/sage/databases/findstat.py   9 doctests failed
>>   src/sage/misc/remote~file~.py2 doctests failed
>>   src/sage/combinat/designs/ext~rep~.py1 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.pyxKilled 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.pyxterminate 
>> 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 

[sage-release] Re: Sage 8.9.rc1 released

2019-09-25 Thread Emmanuel Charpentier
Forgot to specify that these results were for ptestalllong, which is now 
pertinent for Python 3-based Sage...

Incidentally, testing on another machine a patch for ticket Trac#28534 
 (which needed a large 
recompilation), ptest-python3 gives only the well-known failure related to 
FLINT. Currently running ptestalllong on this other machine.

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.pyx2 doctests failed
>   src/sage/coding/databases.py 2 doctests failed
>   src/sage/repl/load.py1 doctest failed
>   src/sage/graphs/graph~latex~.py  2 doctests failed
>   src/sage/databases/findstat.py   9 doctests failed
>   src/sage/misc/remote~file~.py2 doctests failed
>   src/sage/combinat/designs/ext~rep~.py1 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.pyxKilled 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.pyxterminate 
> 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/8897c6c5-c23c-48ec-8f6c-f5a58c35b52e%40googlegroups.com.


[sage-release] Re: Sage 8.9.rc1 released

2019-09-25 Thread Emmanuel Charpentier
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.pyx2 doctests failed
  src/sage/coding/databases.py 2 doctests failed
  src/sage/repl/load.py1 doctest failed
  src/sage/graphs/graph~latex~.py  2 doctests failed
  src/sage/databases/findstat.py   9 doctests failed
  src/sage/misc/remote~file~.py2 doctests failed
  src/sage/combinat/designs/ext~rep~.py1 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.pyxKilled 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.pyxterminate 
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/04d45ad2-fa96-47f3-9df3-da59ef8a2d80%40googlegroups.com.


charpent@p-202-021:/usr/local/sage-python3$ sage -t --long --warn-long 54.9 
src/sage/crypto/mq/sr.py
Running doctests with ID 2019-09-25-13-55-46-2f48cd3b.
Git branch: develop
Using --optional=build,dochtml,dot2tex,fricas,giacpy_sage,memlimit,python2,sage
Doctesting 1 file.
sage -t --long --warn-long 54.9 src/sage/crypto/mq/sr.py
Killed due to abort
**
Tests run before process (pid=21095) failed:
sage: sr = mq.SR(1, 1, 1, 4) ## line 29 ##
sage: sr.n, sr.r, sr.c, sr.e ## line 37 ##
(1, 1, 1, 4)
sage: print(sr.R.repr_long()) ## line 42 ##
Polynomial Ring
  Base Ring : Finite Field in a of size 2^4
   Size : 20 Variables
   Block  0 : Ordering : deglex
  Names: k100, k101, k102, k103, x100, x101, x102, x103, w100, 
w101, 

[sage-release] Re: Sage 8.9.rc1 released

2019-09-25 Thread Eric Gourgoulhon
On Ubuntu 18.04 running on bi-Xeon E5-2623 (8 cores) + 16 GB RAM:


*- python2: *

  - incremental build (from 8.9.rc0, with -j16) OK 
  - all tests from ptestlong passed

- 
*python3: *

  - incremental build (from 8.9.rc0, with -j16) OK 

  - tests from ptest-python3 passed, except for 1 permanent failure in 
   src/sage/rings/polynomial/polynomial_rational_flint.pyx 
   this is the error tracked at https://trac.sagemath.org/ticket/28334

  - tests from ptestlong passed, except for 

--
sage -t --long --warn-long 52.6 src/sage/libs/eclib/interface.py  # 1 
doctest failed
sage -t --long --warn-long 52.6 
src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 1 doctest failed
sage -t --long --warn-long 52.6 src/sage/repl/attach.py  # 4 doctests failed
sage -t --long --warn-long 52.6 src/sage/libs/singular/function.pyx  # 1 
doctest failed
sage -t --long --warn-long 52.6 
src/sage/numerical/backends/generic_backend.pyx  # 2 doctests failed
--

  The failed doctests are those tracked at 
https://trac.sagemath.org/ticket/28298 

  The files
   - src/sage/libs/eclib/interface.py
   - src/sage/rings/polynomial/polynomial_rational_flint.pyx
  have permanent failures, while all doctests in
  - src/sage/repl/attach.py
  - src/sage/libs/singular/function.pyx
  - src/sage/numerical/backends/generic_backend.pyx
  pass when run standalone. 
 
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 sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/9e394d63-b87b-4c1f-8420-8c1176f7878a%40googlegroups.com.