Sage 9.2.beta0 released

172 views
Skip to first unread message

Volker Braun

unread,
May 28, 2020, 5:14:41 PM5/28/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 


860e4dc988 (tag: 9.2.beta0, trac/develop) Updated SageMath version to 9.2.beta0
982d86df0e Trac #29673: spkg-configure.m4 for sympow
84397a0a52 Trac #29666: Serious precision problems with heights of elliptic curve points over number fields
7c71fc3bb1 Trac #29664: get rid of _cmp_ for symbolic expression
2ebe6e5ce0 Trac #29661: Some optimizations for method regions of hyperplane arrangements
c22ec6f190 Trac #29660: Move radius, diameter and eccentricity methods from generic_graph.py to graph.py and digraph.py
4863459703 Trac #29658: Update to BRiAl 1.2.8
9f40d8adee Trac #29656: some gentoo distro info missing
c13e69bf01 Trac #29652: Implement polynomial subresultants
19c8e9cd11 Trac #29645: precision bug in elliptic curve periods (complex embeddings)
cc00c8b1cc Trac #29639: Bug in initialization of vector field with rational components
11021ec846 Trac #29628: Wedge product of multivector field with scalar field
655efd7377 Trac #29611: Direct sum for genus symbols
b42128bed1 Trac #29569: Obtain polar with both Vrep and Hrep (if backend supports it)
e51ad078ce Trac #29568: Initialize polyhedra with backend cdd over RDF with both Vrepresentation and Hrepresentation
6de31119d9 Trac #29469: Have method is_unit of QuotientRingElement and PolynomialQuotientRingElement return True in more cases
5bd59a4d82 Trac #29432: Improve Localization
64efc5e6b4 Trac #29098: Merge build/make/deps into build/make/Makefile.in
10e548884f Trac #29565: Migrate neighborly to combinatorial polyhedron
fbb11c3130 Trac #29502: spkg-configure for suitesparse
36f3858397 Trac #29476: Improvement on numerical modular symbols
e88dfc8837 Trac #29414: Add representation class to docs
58f004f5de Trac #28913: integrate(..., algorithm="giac"): Incorrect conversion to Sage
df2bc13235 Trac #28000: For Sage 9.2: Remove python 2 support from sagelib
9e34d8ff0b Trac #22713: Multiple zeta algebra
805ee2a9f3 Trac #20317: bug in Permutations_msetk cardinality
3c892146f1 Trac #29648: Update src/doc/en/faq
4d756290d4 Trac #29636: Delete changelog sections from all SPKG.txt files
e30cbf5114 Trac #29572: Fix perl_term_readline_gnu build error on conda-forge-macos-maximal
4427340fcd (tag: 9.1, trac/master) Updated SageMath version to 9.1

darwin doppelganger

unread,
May 29, 2020, 1:34:20 PM5/29/20
to sage-release
"make" and "make ptestlong" both succeed on my MacBook pro, Mojave 10.14.6.

Justin C. Walker

unread,
May 30, 2020, 7:08:55 PM5/30/20
to 'Justin C. Walker' via sage-release


> On May 28, 2020, at 14:14 , 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

Pulled fresh clones of the develop tree on the usual three macOS systems:
10.13.6 (2017 iMac Pro, 18-core Xeon W)
10.14.6 (2017 MBP Pro, Quad-core Core i7)
10.15.4 (2019 MBP Pro, 9-core Core i9)

In each case, the build completed without complaint, and all tests (‘ptestlong’) passed!

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
Like the ski resort full of girls hunting for husbands
and husbands hunting for girls, the situation is not
as symmetrical as it might seem.
- Alan MacKay
--

David Coudert

unread,
May 31, 2020, 5:40:56 AM5/31/20
to sage-release
Some tickets merged in 9.2.beta0 are not marked as closed: 29639, 29645, 29652, 29656 ,29658, 29661, 29664, 29673.

Emmanuel Charpentier

unread,
Jun 1, 2020, 1:29:08 PM6/1/20
to sage-release

On Debian testing running o core i7 + 16 GB RAM, pulling Trac#28656 on top of  a 9.1 rebuilt from make distclean (using all the system packages ecommended by ./config) leads to 11 failures (and 1 timeout, which doesn’t when ran standalone) :

File Result P/T
src/sage/schemes/elliptic_curves/ell_number_field.py 3 doctests failed P
src/sage/tests/parigp.py Timed out T
src/sage/rings/number_field/number_field.py 7 doctests failed P
src/sage/rings/number_field/number_field_element.pyx 1 doctest failed P
src/sage/rings/number_field/number_field_ideal.py 2 doctests failed P
src/sage/tests/gap_packages.py 1 doctest failed P
src/sage/numerical/backends/glpk_backend.pyx 1 doctest failed P
src/sage/lfunctions/dokchitser.py 2 doctests failed P
src/sage/rings/polynomial/polynomial_quotient_ring.py 2 doctests failed P
src/sage/lfunctions/pari.py 1 doctest failed P
src/sage/libs/glpk/error.pyx 1 doctest failed P
src/sage/rings/number_field/unit_group.py 1 doctest failed P

The result of re-running these failures is in the attached chkerrs.txt.

Most of these errors were reported for 9.1.rc3, and explained away by Jonathan Kliem. One of them is related to the optional gap_packages package.

HTH,

Le jeudi 28 mai 2020 23:14:41 UTC+2, Volker Braun a écrit :

chkerrs.txt

Sébastien Labbé

unread,
Jun 3, 2020, 8:13:24 AM6/3/20
to sage-release
Testing various optional and external packages, I get

Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,sage_numerical_backends_cplex,sage_numerical_backends_gurobi

----------------------------------------------------------------------
sage -t --long src/sage/databases/findstat.py  # 17 doctests failed
sage -t --long src/sage/databases/oeis.py  # 1 doctest failed
sage -t --long src/sage/geometry/polyhedron/base.py  # Bad exit: 1
sage -t --long src/sage/graphs/generators/smallgraphs.py  # 2 doctests failed
sage -t --long src/sage/sat/boolean_polynomials.py  # 1 doctest failed
----------------------------------------------------------------------
External software detected for doctesting: cplex,ffmpeg,graphviz,imagemagick,internet,latex,pandoc

The boolean_polynomial failure (seen before, copied below) does not reappear on a second run:

----------------------------------------------------------------------
sage -t --long src/sage/databases/findstat.py  # 17 doctests failed
sage -t --long src/sage/databases/oeis.py  # 1 doctest failed
sage -t --long src/sage/geometry/polyhedron/base.py  # Bad exit: 1
sage -t --long src/sage/graphs/generators/smallgraphs.py  # Killed due to abort
----------------------------------------------------------------------
External software detected for doctesting: internet

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


sage -t --long 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>
**********************************************************************
1 item had failures:
   1 of  41 in sage.sat.boolean_polynomials.solve
    0 tests not run because we ran out of time
    [46 tests, 1 failure, 182.57 s]

Reply all
Reply to author
Forward
0 new messages