Sage 10.0.rc3 released

147 views
Skip to first unread message

Volker Braun

unread,
May 12, 2023, 4:40:54 PM5/12/23
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


f2f5863c08a (tag: 10.0.rc3, github/develop) Updated SageMath version to 10.0.rc3
937f7d915f9 gh-35625: `zeromq`: Add system package info for Arch Linux, Gentoo
49e5c41f33f gh-35571: update openssl to 3.0.8
8aa721379a5 (tag: 10.0.rc2) Updated SageMath version to 10.0.rc2

Matthias Köppe

unread,
May 13, 2023, 5:54:55 PM5/13/23
to sage-release
Thanks for the new rc. Tests ran at https://github.com/sagemath/sage/actions/runs/4962805314

All "standard" configurations on the tested Linux platform look OK - except:
Segmentation faults in sage.libs.gap

Build errors in the "minimal" configuration on fedora-38, archlinux-latest, opensuse-tumbleweed are still present.
This will need the OpenBLAS update from https://github.com/sagemath/sage/pull/35371 (needs review).
Other relevant tickets for the 10.0 release: https://github.com/sagemath/sage/milestone/152

Volker Braun

unread,
May 14, 2023, 4:48:30 AM5/14/23
to sage-release
As always, only blockers are merged in release candidates. If a normal ticket is not done during the normal merge window then its not going in, otherwise we never finish making a release.

Dima Pasechnik

unread,
May 14, 2023, 5:05:19 AM5/14/23
to sage-release


On Sun, 14 May 2023, 09:48 Volker Braun, <vbrau...@gmail.com> wrote:
As always, only blockers are merged in release candidates. If a normal ticket is not done during the normal merge window then its not going in, otherwise we never finish making a release.

Volker, can you at least merge small documentation or dependency lists only things before the release?
i.e. PRs 35637 and 35638

Without them, we'd potentially get more bug/problems reports here - for bugs which aren't bugs, or bugs which are fixed.
This is potentially much more work even for us, at expense of your 2 minutes or so needed to merge trivial changes.







On Saturday, May 13, 2023 at 11:54:55 PM UTC+2 matthia...@gmail.com wrote:
Other relevant tickets for the 10.0 release: https://github.com/sagemath/sage/milestone/152

--
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/17850ffb-9e4f-44fb-96bf-dd9e10c3fdd3n%40googlegroups.com.

Volker Braun

unread,
May 14, 2023, 5:14:32 AM5/14/23
to sage-release
On Sunday, May 14, 2023 at 11:05:19 AM UTC+2 Dima Pasechnik wrote:
i.e. PRs 35637 and 35638

OK, will do.

Matthias Köppe

unread,
May 14, 2023, 2:23:29 PM5/14/23
to sage-release
Note that  what's left in the 10.0 milestone is already hand-picked. https://github.com/sagemath/sage/milestone/152

In particular, could you please merge https://github.com/sagemath/sage/pull/35460 (the update to our developer's guide for GitHub -- didn't you say the transition to GitHub is marked by the 10.0 release?)

John H Palmieri

unread,
May 15, 2023, 5:13:03 PM5/15/23
to sage-release
I consistently see these failures on various OS X machines:

sage -t --long --random-seed=244618093388694547212515065258622925284 src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
sage -t --long --random-seed=244618093388694547212515065258622925284 src/sage/libs/giac/__init__.py  # Timed out

I've seen these reported after earlier releases. Is there a ticket?

On Friday, May 12, 2023 at 1:40:54 PM UTC-7 Volker Braun wrote:

Kwankyu Lee

unread,
May 15, 2023, 9:05:25 PM5/15/23
to sage-release
On Tuesday, May 16, 2023 at 6:13:03 AM UTC+9 John H Palmieri wrote:
I consistently see these failures on various OS X machines:

sage -t --long --random-seed=244618093388694547212515065258622925284 src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
sage -t --long --random-seed=244618093388694547212515065258622925284 src/sage/libs/giac/__init__.py  # Timed out

I've seen these reported after earlier releases. Is there a ticket?

For me, they pass with SageMath version 10.0.rc2. I am on macOS 12.6.5 with Intel Xeon E5.  

What is the failed doctest?

Kenji Iohara

unread,
May 16, 2023, 11:01:23 AM5/16/23
to sage-r...@googlegroups.com
I also had the same failures since several versions on Mac OS 13.3.1a with Intel Core i5 machine.

2023年5月15日(月) 23:13 John H Palmieri <jhpalm...@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.

John H Palmieri

unread,
May 16, 2023, 3:58:56 PM5/16/23
to sage-release
On an iMac Pro (some Intel chip), the first failure (rings/polynomial/multi_polynomial_ideal.py) is also related to giac:

sage: A9=PolynomialRing(QQ,9,'x') ## line 4225 ##
sage: I9=sage.rings.ideal.Katsura(A9) ## line 4226 ##
sage: print("possible output from giac", flush=True); I9.groebner_basis("giac",proba_epsilon=1e-7) # long time (3s) ## line 4227 ##
possible output from giac
------------------------------------------------------------------------
0   signals.cpython-311-darwin.so       0x000000010edc1582 print_backtrace + 66
1   signals.cpython-311-darwin.so       0x000000010edc40b3 sigdie + 67
2   signals.cpython-311-darwin.so       0x000000010edc3fa9 cysigs_signal_handler + 505
3   libsystem_platform.dylib            0x00007ff81a2185ed _sigtramp + 29
4   ???                                 0x0000000000000000 0x0 + 0
5   libgiac.0.dylib                     0x00000001780b7e7e _ZN4giac10do_zbuildMINS_8tdeg_t14EEEvRKNS_12vectzpolymodIT_EERKNSt3__16vectorIjNS7_9allocatorIjEEEEibRKNS8_INS8_IS3_NS9_IS3_EEEENS9_ISF_EEEERKSF_RKNS8_IiNS9_IiEEEEPvRNS8_INS_12coeffindex_tENS9_ISR_EEEEjRNS8_INS8_ItNS9_ItEEEENS9_ISW_EEEERNS8_ISN_NS9_ISN_EEEERNS8_INS_14sparse_elementENS9_IS13_EEEEiii + 334
6   libgiac.0.dylib                     0x00000001780b7d12 _ZN4giac8zbuildM_INS_8tdeg_t14EEEPvS2_ + 114
7   libsystem_pthread.dylib             0x00007ff81a1eb1d3 _pthread_start + 125
8   libsystem_pthread.dylib             0x00007ff81a1e6bd3 thread_start + 15
------------------------------------------------------------------------
Unhandled SIGSEGV during signal handling.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.
-----------------------------------------------


The second one (giac/__init__.py) times out. The log file says

Tests run before process (pid=64629) timed out:
sage: from sage.libs.giac import groebner_basis as gb_giac # random ## line 15 ##
sage: P = PolynomialRing(QQ, 6, 'x') ## line 16 ##
sage: I = sage.rings.ideal.Cyclic(P) ## line 17 ##
sage: B = gb_giac(I.gens()) # random ## line 18 ##

John H Palmieri

unread,
May 16, 2023, 5:40:07 PM5/16/23
to sage-release
I see the same failures on a laptop with an M2 chip.

G. M.-S.

unread,
May 16, 2023, 6:35:15 PM5/16/23
to sage-r...@googlegroups.com

This is on Apple Silicon Macs ("M" series) with Homebrew up to date (including OpenBLAS), on macOS 11.7.6 (Xcode 13.2.1), macOS 12.6.5 (Xcode 14.2) and macOS 13.3.1(a) (Xcode 14.3).

For John, Kwankyu and Kenji:  Same results as with 10.0.beta8.  In particular, problems with
src/sage/rings/polynomial/multi_polynomial_ideal.py
src/sage/libs/giac/__init__.py
do not appear with macOS 11.7.6 and 12.6.5.

To make make work, make -j1 was not needed.

After make and make pytest (which succeed) make ptestlong gives

sage -t --long --warn-long … --random-seed=… src/sage/modular/modform_hecketriangle/abstract_space.py  # 3 doctests failed
sage -t --long --warn-long … --random-seed=… src/sage/modular/modform_hecketriangle/readme.py  # 1 doctest failed
sage -t --long --warn-long … --random-seed=… src/sage/modular/modform_hecketriangle/space.py  # 2 doctests failed

sage -t --long --warn-long 26.5 --random-seed=164104516405977008420373837524113607070 src/sage/quadratic_forms/binary_qf.py  # 1 doctest failed

On macOS 11.7.6:
sage -t --long --warn-long … --random-seed=… src/sage/matrix/matrix_gf2e_dense.pyx  # 1 doctest failed

On macOS 13.3.1(a):
sage -t --long --warn-long 30.6 --random-seed=… src/sage/rings/polynomial/multi_polynomial_ideal.py  # 1 doctest failed
sage -t --long --warn-long 30.6 --random-seed=… src/sage/libs/giac/__init__.py  # Killed due to kill signal

Guillermo

John H Palmieri

unread,
May 16, 2023, 6:45:06 PM5/16/23
to sage-release
Thank you, Guillermo. I should have said: I'm using OS X 13.3.1 on both machines where I'm seeing these failures. I created https://github.com/sagemath/sage/issues/35646 for this.

G. M.-S.

unread,
May 19, 2023, 5:23:36 PM5/19/23
to sage-r...@googlegroups.com

This is on Apple Silicon Macs ("M" series) with Homebrew up to date.

Just a quick note to let you know that after updating the OS to
macOS 11.7.7
macOS 12.6.6
macOS 13.4
the results are the same.

Guillermo
Reply all
Reply to author
Forward
0 new messages