Sage 8.3.rc3 released
107 views
Skip to first unread message
Volker Braun
Jul 28, 2018, 7:58:33 AM7/28/18
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
Barring any unforseen changes this should be the last rc...
1615f58890 (tag: 8.3.rc3, trac/develop) Updated SageMath version to 8.3.rc3
80e76cae02 Trac #25912: Infinite loop in pkg-config
e52ff8ba1b Trac #25379: random failure in QuadraticResidueCodeOddPair
f608d821e8 (tag: 8.3.rc2) Updated SageMath version to 8.3.rc2
Emmanuel Charpentier
Jul 28, 2018, 3:38:06 PM7/28/18
to sage-release
FWIW, (incrementally) builds and passes ptestlong on Debian testing running on core i7 + 16 GB RAM without errors whatsoever.
HTH,
--
Emmanuel Charpentier
HTH,
--
Emmanuel Charpentier
Justin C. Walker
Jul 28, 2018, 5:04:02 PM7/28/18
to sage-r...@googlegroups.com
> On Jul 28, 2018, at 04:58 , 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
>
Built w/o problems from a fresh clone of the develop tree (macOS 10.11.6, Quad-core Core i7). All tests (‘ptestlong’) passed!
Justin
--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's Income
-----------
Nobody knows the trouble I've been
-----------
Eric Gourgoulhon
Jul 30, 2018, 5:40:13 AM7/30/18
to sage-release
On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git
clone +
pull develop,
parallel (-j16) build OK and make ptestlong failed with
sage -t --long --warn-long 49.0 src/sage/numerical/backends/logging_backend.py # Killed due to abort
I am attaching the relevant part of the log file.
The test is passed though when run standalone:
./sage -t --long --warn-long 49.0 src/sage/numerical/backends/logging_backend.py
Running doctests with ID 2018-07-30-11-36-50-76127019.
Git branch: develop
Using --optional=mpir,python2,sage
Doctesting 1 file.
sage -t --long --warn-long 49.0 src/sage/numerical/backends/logging_backend.py
[46 tests, 0.46 s]
----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
Total time for all tests: 0.5 seconds
cpu time: 0.5 seconds
cumulative wall time: 0.5 seconds
Running doctests with ID 2018-07-30-11-36-50-76127019.
Git branch: develop
Using --optional=mpir,python2,sage
Doctesting 1 file.
sage -t --long --warn-long 49.0 src/sage/numerical/backends/logging_backend.py
[46 tests, 0.46 s]
----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
Total time for all tests: 0.5 seconds
cpu time: 0.5 seconds
cumulative wall time: 0.5 seconds
Eric.
Emmanuel Charpentier
Jul 30, 2018, 8:21:18 AM7/30/18
to sage-release
FWIW, on a slightly smaller machine (core i5, 8 GB RAM, Debian testing), I got a transient failure :
----------------------------------------------------------------------
sage -t --long --warn-long 48.7 src/sage/doctest/external.py # 3 doctests failed
----------------------------------------------------------------------
which turns out to be three timeouts in internet access. The test passes with no failure when ran standalone. The problem might be but do our corporate firewall/cache, which happens not to to be above all praise...
HTH,
--
Emmanuel Charpentier
Reply all
Reply to author
Forward
0 new messages