Re: [sage-release] Sage 9.4 released

Tue, 24 Aug 2021 13:20:27 -0700 


> On Aug 22, 2021, at 05:04 , [email protected] <[email protected]> wrote:
> 
> The "master" git branch has been updated to Sage-9.5. 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
> 
> There was no change over 9.4.rc2
> 
> 488ced5dc4 (tag: 9.4, trac/master, trac/develop) Updated SageMath version to 
> 9.4
> 7282b2b6c6 (tag: 9.4.rc2) Updated SageMath version to 9.4.rc2

Built and tested on three macOS platforms.  All builds completed without 
problems.  Testing (‘ptestlong’) went as follows:

10.13.6 (2017 iMac Pro, 18-core Xeon W): One failure
   sage -t --long --warn-long 69.2 --random-seed=0 
src/sage/geometry/polyhedron/base.py
   [the usual flakey “get_memory_usage()” test]

10.14.6 (2017 MBP, 4-core Core i7): Two failures
  sage -t --long --warn-long 135.2 --random-seed=0 
src/sage/graphs/bipartite_graph.py
  [usual intermittent “expected 0.0, got something different” failure]
  sage -t --long --warn-long 135.2 --random-seed=0 
src/sage/symbolic/integration/external.py
  [this one seems persistent: two exceptions following a “KeyError: sageVAR”]

10.15.7 (2019 MBP, 8-core Core i9): One failure
  sage -t --long --warn-long 135.2 --random-seed=0 
src/sage/graphs/bipartite_graph.py
  [usual intermittent “expected 0.0, got something different” failure]

Almost the same as 9.4.rc2 :-}

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk
--------



-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/32F4479B-B581-438E-8F95-C0F689D9DFB5%40mac.com.























					Reply via email to