Sage 9.2.rc3 released

Volker Braun

unread,

Oct 18, 2020, 6:01:45 AM10/18/20

to sage-release

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

f976c52c57 (tag: 9.2.rc3, trac/develop) Updated SageMath version to 9.2.rc3

70d165564b Trac #30402: Cannot load an object containing a matrix if it was saved from Python 2 Sage

3ac4f4acd4 Trac #30643: cygwin-minimal, cygwin-standard: scipy build fails: 'u_int' has not been declared

dc3fc00492 Trac #30687: "make python3-clean" should always remove local/bin/python3*

2b5c0ba2c0 Trac #30757: fedora-33-standard/homebrew-macos flint/arb breakage

c5ca85e1fb Trac #30758: for python 3.6, universal_newlines=, not text=, must be used in run()

1e728ac0d3 (tag: 9.2.rc2) Updated SageMath version to 9.2.rc2

Emmanuel Charpentier

unread,

Oct 20, 2020, 1:56:33 PM10/20/20

to sage-release

On Debian testing running on core i7 + 16 GB RAM, after upgrading 0.2.rc1 to 9.2.rc3 configured to use all available system packages, ptestlong results in one transient and five permanent failures, four already reported for previous versions :

File	Resulte	P/T
src/sage/schemes/hyperelliptic_curves/monsky_washnitzer.py	Killed due to abort	P
src/sage/tests/parigp.py	Timed out	T
src/sage/modules/fg_pid/fgp_module.py	3 doctests failed	P
src/doc/en/developer/coding_in_other.rst	1 doctest failed	P
src/doc/en/constructions/algebraic_geometry.rst	1 doctest failed	P
src/sage/modules/free_module_morphism.py	3 doctests failed	P

Repetition of the “new” failing test fgp_module.py results in the following :

sage -t --long --warn-long 170.4 --random-seed=0 src/sage/modules/fg_pid/fgp_module.py
**********************************************************************
File "src/sage/modules/fg_pid/fgp_module.py", line 130, in sage.modules.fg_pid.fgp_module
Failed example:
    y = f.lift(3*M1.0); y
Expected:
    (0, 13)
Got:
    (1, 0)
**********************************************************************
File "src/sage/modules/fg_pid/fgp_module.py", line 1288, in sage.modules.fg_pid.fgp_module.FGP_Module_class.coordinate_vector
Failed example:
    Q.coordinate_vector(-x, reduce=False)
Expected:
    (0, -4)
Got:
    (0, 8)
**********************************************************************
File "src/sage/modules/fg_pid/fgp_module.py", line 1417, in sage.modules.fg_pid.fgp_module.FGP_Module_class.optimized
Failed example:
    X
Expected:
    [0 4 0]
    [0 1 0]
    [0 0 1]
Got:
    [ 0 -8  0]
    [ 0  1  0]
    [ 0  0  1]
**********************************************************************
3 items had failures:
   1 of  45 in sage.modules.fg_pid.fgp_module
   1 of  23 in sage.modules.fg_pid.fgp_module.FGP_Module_class.coordinate_vector
   1 of  11 in sage.modules.fg_pid.fgp_module.FGP_Module_class.optimized
    [396 tests, 3 failures, 2.84 s]
----------------------------------------------------------------------
sage -t --long --warn-long 170.4 --random-seed=0 src/sage/modules/fg_pid/fgp_module.py  # 3 doctests failed
----------------------------------------------------------------------
Total time for all tests: 2.9 seconds
    cpu time: 2.8 seconds
    cumulative wall time: 2.8 seconds

HTH,

Kenji Iohara

unread,

Oct 20, 2020, 2:20:59 PM10/20/20

to sage-r...@googlegroups.com

On Mac OS 10.15.7 with Xcode 12, I could compile it from the first buit, but for

make ptestlong, I have the next errors:

2020年10月18日(日) 12:01 Volker Braun <vbrau...@gmail.com>:

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/456c94f5-e308-4e69-aa7a-ceac90e1c9f1n%40googlegroups.com.

ptestlong.log

Clemens Heuberger

unread,

Oct 21, 2020, 1:40:53 PM10/21/20

to sage-r...@googlegroups.com

On one machine (Linux Mint 18.2 Sonya) (which also serves as a patchbot which I
now disabled due to this problem) I still have the reproducible segmentation
fault in src/sage/interfaces/singular.py reported in
https://groups.google.com/d/msg/sage-release/H8wldUuFtVg/GD1UldTCAQAJ .
Log attached.

git bisect tells me that commit

cb9bd8e3ff build/pkgs/sympy: Update to 1.6.2

(part of Trac #30425) is the first commit where such a segfault happens.
(I should note that I did not make distclean in my git bisect runs in order to
get a result in finite time; I will do that now before and after that ticket and
will report back afterwards).

Am 18.10.20 um 12:01 schrieb Volker Braun:

> --
> 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...@googlegroups.com

> <mailto:sage-release...@googlegroups.com>.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/456c94f5-e308-4e69-aa7a-ceac90e1c9f1n%40googlegroups.com

> <https://groups.google.com/d/msgid/sage-release/456c94f5-e308-4e69-aa7a-ceac90e1c9f1n%40googlegroups.com?utm_medium=email&utm_source=footer>.

singular-crash.log

Dima Pasechnik

unread,

Oct 21, 2020, 2:05:14 PM10/21/20

to sage-release

On Wed, Oct 21, 2020 at 6:40 PM Clemens Heuberger
<clemens....@aau.at> wrote:
>
> On one machine (Linux Mint 18.2 Sonya) (which also serves as a patchbot which I
> now disabled due to this problem) I still have the reproducible segmentation
> fault in src/sage/interfaces/singular.py reported in
> https://groups.google.com/d/msg/sage-release/H8wldUuFtVg/GD1UldTCAQAJ .
> Log attached.
>
> git bisect tells me that commit
>
> cb9bd8e3ff build/pkgs/sympy: Update to 1.6.2
>
> (part of Trac #30425) is the first commit where such a segfault happens.
> (I should note that I did not make distclean in my git bisect runs in order to
> get a result in finite time; I will do that now before and after that ticket and
> will report back afterwards).

I certainly saw this "unfinished input" test crashing on more than one system

sage: _ = singular._expect.sendline('1+') # unfinished input ## line 504 ##
sage: try:
alarm(0.5)
singular._expect_expr('>') # interrupt this
except KeyboardInterrupt:
pass ## line 505 ##
Control-C pressed. Interrupting Singular. Please wait a few seconds...
sage: 2*a ## line 514 ##
------------------------------------------------------------------------
/local/sage-patchbot/sage/local/lib/python3.8/site-packages/cysignals/signals.cpython-38-x86_64-linux-gnu.so(+0x7f08)[0x7f353e6bdf08]

This is a pexpect trouble IMHO...

> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/11deccab-5404-87a1-05f1-a11266513e37%40aau.at.

Clemens Heuberger

unread,

Oct 22, 2020, 12:35:19 PM10/22/20

to sage-r...@googlegroups.com

Strangely enough, make distclean and then make ptestlong made the error go away
after the ticket which caused problems yesterday; Trac #30425. So I try to
refine my git bisection.

Am 21.10.20 um 19:41 schrieb Clemens Heuberger:

Sébastien Labbé

unread,

Oct 22, 2020, 4:12:47 PM10/22/20

to sage-release

Using Ubuntu 18.04, trying to test with optional + external packages, I still get the tests to stop at half of the execution, and I still don't know why.

The exact command I run is:

./sage -t -p --all --long --optional=sage,optional,external --show-skipped --logfile=logs/ptestallshowskipped.log

I obtain:

Using --optional=4ti2,cbc,ccache,cryptominisat,database_jones_numfield,debian,dot2tex,e_antic,external,fricas,glucose,latte_int,libnauty,lidia,lrslib,memlimit,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,sage_spkg

[...]

sage -t --long --warn-long 70.0 --random-seed=0 src/sage/sat/boolean_polynomials.py
**********************************************************************
File "src/sage/sat/boolean_polynomials.py", line 86, in sage.sat.boolean_polynomials.solve
Failed example:
    s = solve_sat(F, s_verbosity=1, c_max_vars_sparse=4, c_cutting_number=8) # optional - cryptominisat
Expected:
    c ...
    ...
Got:
    <BLANKLINE>
Killing test src/sage/sat/boolean_polynomials.py
Killing test src/sage/quadratic_forms/quadratic_form__neighbors.py
Killing test src/sage/interfaces/octave.py
Killing test src/sage/interfaces/fricas.py
Killing test src/sage/doctest/external.py
Killing test src/sage/categories/r_trivial_semigroups.py
----------------------------------------------------------------------
sage -t --long --warn-long 70.0 --random-seed=0 src/doc/en/constructions/interface_issues.rst # 1 doctest failed
sage -t --long --warn-long 70.0 --random-seed=0 src/sage/databases/findstat.py # 2 doctests failed
sage -t --long --warn-long 70.0 --random-seed=0 src/sage/lfunctions/sympow.py # 4 doctests failed
sage -t --long --warn-long 70.0 --random-seed=0 src/sage/schemes/elliptic_curves/ell_rational_field.py # 2 doctests failed
Doctests interrupted: 2295/4211 files tested
----------------------------------------------------------------------
Total time for all tests: 1882.0 seconds
    cpu time: 12995.1 seconds
    cumulative wall time: 14651.3 seconds

The above failures obtained before interruption are already reported at https://trac.sagemath.org/ticket/25536

Emmanuel Charpentier

unread,

Oct 22, 2020, 7:56:06 PM10/22/20

to sage-release

ptestalllong stopped working for me for a lohg time (since I switched to Python 3-based compilatins, IIRC).

HTH,

David Coudert

unread,

Oct 23, 2020, 3:24:46 AM10/23/20

to sage-r...@googlegroups.com

On macOS 10.15.17, I noticed a weird behavior with tab completion.

See attached screenshots.

When I add a " , then tab completion works as expected.

sage: cd "./src/sage/graphs/"

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/456c94f5-e308-4e69-aa7a-ceac90e1c9f1n%40googlegroups.com.

Dima Pasechnik

unread,

Oct 23, 2020, 4:41:36 AM10/23/20

to sage-release

On Fri, Oct 23, 2020 at 8:24 AM David Coudert <david....@gmail.com> wrote:

On macOS 10.15.17, I noticed a weird behavior with tab completion.

this is not macOS-specific, happens on Linux as well.

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/9072BB67-A80B-42DB-9D89-BBD86286980E%40gmail.com.

Sébastien Labbé

unread,

Oct 23, 2020, 7:26:31 AM10/23/20

to sage-release

> Using Ubuntu 18.04, trying to test with optional + external packages, I still get the tests to stop at half of the execution, and I still don't know why.

Reducing the number of CPUs to -j5 instead of -j8, I managed to get all tests to run. I get no other failures than the one reported above:

----------------------------------------------------------------------

sage -t --long --warn-long 69.9 --random-seed=0 src/sage/schemes/elliptic_curves/ell_rational_field.py # 2 doctests failed

sage -t --long --warn-long 69.9 --random-seed=0 src/sage/databases/findstat.py # 2 doctests failed
sage -t --long --warn-long 69.9 --random-seed=0 src/sage/lfunctions/sympow.py # 4 doctests failed
sage -t --long --warn-long 69.9 --random-seed=0 src/doc/en/constructions/interface_issues.rst # 1 doctest failed

----------------------------------------------------------------------

External software detected for doctesting: ffmpeg,graphviz,imagemagick,internet,latex,octave,pandoc

Follow up at https://trac.sagemath.org/ticket/25536

Reply all

Reply to author

Forward