Sage 9.0.beta3 released

Volker Braun

unread,

Oct 26, 2019, 7:48:46 PM10/26/19

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

906b12b1e2 (tag: 9.0.beta3, trac/develop) Updated SageMath version to 9.0.beta3

4e12d998bc Trac #28562: Tensor Fields: Better Zero Treatment

78d7905fc3 Trac #28531: bliss canonical labels ignores edge labels

9b8f10e98f Trac #28642: Silence pyflakes warning

3a0581721d Trac #28601: some typos and https

ceee1d48ad Trac #28463: .neighbors() error in polyhedron.representation

c4738d71aa Trac #28159: Vector Bundles

7f4acc39f8 Trac #20264: Hasse-Weil Zeta function of a cyclic cover of P1 over finite fields.

1ece1cfe12 Trac #28636: refresh the pieri_factors file

6d35e3a139 Trac #28619: Reference manual doesn't build with --include-tests-blocks

0bdecde0d4 Trac #28637: remove deprecated alias for algebraic dependency

948658943c Trac #28631: Implement polynomial factorization over universal cyclotomic field

f2e5a05dd9 Trac #28625: Let CombinatorialPolyhedron handle f_vector of polyhedra

c07209551d Trac #28621: Add CombinatorialPolyhedron method to Polyhedron objects

e745a8cb7c Trac #28604: CombinatorialPolyhedron: ridge_graph -> facet_graph

847b27812f Trac #28603: CombinatorialPolyhedron: edge_graph -> vertex_graph

adf7c6f30a Trac #28600: Use standard notation for pullback and pushforward on manifolds

dafcaac1cb Trac #28155: Check for formality of GCDA's

b81bb55ef2 Trac #27813: Implement _im_gens_ for LaurentPolynomial_mpair

76b7fdd115 (tag: 9.0.beta2) Updated SageMath version to 9.0.beta2

Emmanuel Charpentier

unread,

Oct 27, 2019, 2:16:12 PM10/27/19

to sage-release

On Debian testing running on core i7 + 16 GB RAM, the upgrade of a Python 3-base 9.0.beta2 to 9.0.beta3 gives results close to those already reported:

Permanent failures :

File | Result

--------------------------------------------------------+-----------------

src/sage/tests/gap_packages.py | 1 doctest failed

src/sage/rings/polynomial/polynomial_rational_flint.pyx | 1 doctest failed

Transient failures :

File | Result

--------------------------------------------------------+------------------

src/sage/graphs/generators/smallgraphs.py | 6 doctests failed

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/modular/ssmod/ssmod.py | 2 doctests failed

src/sage/coding/databases.py | 2 doctests failed

src/sage/misc/latex.py | 1 doctest failed

src/sage/misc/persist.pyx | 2 doctests failed

src/sage/repl/load.py | 1 doctest failed

src/sage/graphs/graph_latex.py | 2 doctests failed

src/sage/combinat/designs/ext_rep.py | 1 doctest failed

src/sage/misc/remote_file.py | 2 doctests failed

src/sage/databases/findstat.py | 9 doctests failed

The transient failure on ssmod.py wasn't seen previously. OTOH, I've fiddled with the CPU speed control of the machine...

HTH,

Emmanuel Charpentier

unread,

Oct 28, 2019, 5:49:49 AM10/28/19

to sage-release

FWIW, on Debian testing running on a smaller machine (core i5 + 8 GB RAM, no gap_packages installed), upgrading a Python 3-based 9.0.beta2 to 9.0.beta3 gives the usual ptestalllong failures:

Permanent failures :

File | Result

--------------------------------------------------------+-----------------

src/sage/rings/polynomial/polynomial_rational_flint.pyx | 1 doctest failed

Transient failures :

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 | 9 doctests failed

src/sage/interfaces/magma_free.py | 2 doctests failed

HTH,

Eric Gourgoulhon

unread,

Oct 28, 2019, 7:06:21 AM10/28/19

to sage-release

On Ubuntu 18.04 running on bi-Xeon E5-2623 (8 cores) + 16 GB RAM and for a python3 build:

- incremental build (from 9.0.beta2, with -j16) OK

- tests from ptestlong passed, except for

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

Hopefully, these failures are fixed by

https://trac.sagemath.org/ticket/28334

and

https://trac.sagemath.org/ticket/28622

which should be merged in Sage 9.0.beta4.

Eric.

Justin C. Walker

unread,

Oct 31, 2019, 8:26:00 PM10/31/19

to 'Justin C. Walker' via sage-release

> On Oct 26, 2019, at 16:48 , Volker Braun <vbrau...@gmail.com> wrote:
>
> 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

The build (from a fresh clone of the develop branch) succeeded w/o problems on three macOS systems: 10.11.6 (mid-2015 MBP, Quad-core i7); 10.13.6 (2017 iMac Pro, 18-core Xeon W); and 10.14.6 (2017 MBP, Quad-core i7).

Testing (‘ptestlong’) yielded the following:
- 10.11.6: all tests passed.
- 10.13.6: all tests passed.
- 10.14.6: all tests passed.

Ship it!

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
My wife 'n kids 'n dogs are gone,
I can't get Jesus on the phone,
But Ol' Milwaukee's Best is my best friend.
-----------

Reply all

Reply to author

Forward