Sage 8.3 released

Volker Braun

unread,

Aug 3, 2018, 7:47:49 AM8/3/18

to sage-release

The "master" git branch has been updated to Sage-8.3. 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 8.3.rc3

For the two people that wanted a calendar-driven release schedule: The merge window will be open until October 1st, 2018. We can experiment and see how this works out.

Vincent Delecroix

unread,

Aug 3, 2018, 3:09:30 PM8/3/18

to sage-r...@googlegroups.com

Thanks Volker! I forwarded this information in the 8.4 milestone of our
trac server.

Vincent

Justin C. Walker

unread,

Aug 4, 2018, 1:44:21 AM8/4/18

to sage-r...@googlegroups.com

> On Aug 3, 2018, at 04:47 , Volker Braun <vbrau...@gmail.com> wrote:
>
> The "master" git branch has been updated to Sage-8.3. 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 from fresh clone of the develop branch on two systems without problems:

macOS 10.11.6 (Quad-core Vore i7 mid-2015 MBP): testing (‘ptestlong’) with all tests passing.

macOS 10.13.6 (Quad-core Vore i7 2017 MBP): testing (‘ptestlong’) with three issues:

sage -t --long --warn-long 241.7 src/sage/combinat/designs/ext_rep.py # Killed due to abort
sage -t --long --warn-long 241.7 src/sage/doctest/external.py # Killed due to abort
sage -t --long --warn-long 241.7 src/sage/interfaces/singular.py # 1 doctest failed

When run singly, the first two persisted, the last succeeded. Attaching log of the three singleton tests. FWIW, I sometimes get a popup alert to ignore faults or report. Sometimes when I do, clicking gives me a window with more information, and in the case of the two latter crashes, there was a comment to the effect that the crash occurred (in python 2.7) between fork and pre-exec, As I said, I sometimes get these, but trying to verify the exact wording, I only got the alert; clicking report probably sent the report to Apple, untouched.

Anyone else seen this? I can’t be sure this is Sage, because my shiny new 2017 MBP is behaving psychotically. A lot of performance problems and UI lockups.

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
I want to die, peacefully in my sleep, like my grandfather;
not screaming in terror, like his passengers.

Jan Groenewald

unread,

Aug 4, 2018, 7:23:39 AM8/4/18

to sage-release

Hi

On Fri, 3 Aug 2018 at 13:47, Volker Braun <vbrau...@gmail.com> wrote:

The "master" git branch has been updated to Sage-8.3. 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

Fails to build for me on debian 9 stretch in a qemu-kvm virtual image with 2G RAM.

Openblas log attached.

Regards,

Jan

--

.~.
/V\ Jan Groenewald
/( )\ www.aims.ac.za
^^-^^

openblas-0.2.20.p2.log.xz

bryan gin-ge chen

unread,

Aug 4, 2018, 8:50:13 AM8/4/18

to sage-release

On Saturday, August 4, 2018 at 1:44:21 AM UTC-4, Justin C. Walker wrote:
>
> Built from fresh clone of the develop branch on two systems without problems:
>
> macOS 10.11.6 (Quad-core Vore i7 mid-2015 MBP): testing (‘ptestlong’) with all tests passing.
>
> macOS 10.13.6 (Quad-core Vore i7 2017 MBP): testing (‘ptestlong’) with three issues:
>
> sage -t --long --warn-long 241.7 src/sage/combinat/designs/ext_rep.py # Killed due to abort
> sage -t --long --warn-long 241.7 src/sage/doctest/external.py # Killed due to abort
> sage -t --long --warn-long 241.7 src/sage/interfaces/singular.py # 1 doctest failed
>
> When run singly, the first two persisted, the last succeeded. Attaching log of the three singleton tests. FWIW, I sometimes get a popup alert to ignore faults or report. Sometimes when I do, clicking gives me a window with more information, and in the case of the two latter crashes, there was a comment to the effect that the crash occurred (in python 2.7) between fork and pre-exec, As I said, I sometimes get these, but trying to verify the exact wording, I only got the alert; clicking report probably sent the report to Apple, untouched.
>
> Anyone else seen this? I can’t be sure this is Sage, because my shiny new 2017 MBP is behaving psychotically. A lot of performance problems and UI lockups.
>

The first two failed tests are most likely caused by this issue:

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

The solution is to run

export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES

before the tests.

Emmanuel Charpentier

unread,

Aug 4, 2018, 5:39:08 PM8/4/18

to sage-release

On Debian testing runninng on Core i7 + 16 GB RAM, I get one (transient) failure :

sage -t --long src/sage/doctest/test.py

**********************************************************************

File "src/sage/doctest/test.py", line 164, in sage.doctest.test

Failed example:

subprocess.call(["sage", "-t", "--warn-long", "0", "99seconds.rst"], **kwds2) # long time

Expected:

Running doctests...

Doctesting 1 file.

sage -t --warn-long 0.0 99seconds.rst

Timed out

**********************************************************************

Tests run before process (pid=...) timed out:

...

----------------------------------------------------------------------

sage -t --warn-long 0.0 99seconds.rst # Timed out

----------------------------------------------------------------------

...

4

Got:

Running doctests with ID 2018-08-04-21-48-56-7cb17d13.

Git branch: develop

Using --optional=database_gap,dot2tex,fricas,giacpy_sage,gmpy2,igraph,mpir,python2,python_igraph,sage

Doctesting 1 file.

sage -t --warn-long 0.0 99seconds.rst

Timed out (and interrupt failed)

**********************************************************************

Tests run before process (pid=16110) timed out:

sage: import time ## line 3 ##

sage: time.sleep(99) ## line 4 ##

------------------------------------------------------------------------

/usr/local/sage-8/local/lib/python2.7/site-packages/cysignals/signals.so(+0x6c68)[0x7faa8eeb3c68]

/usr/local/sage-8/local/lib/python2.7/site-packages/cysignals/signals.so(+0x6d0f)[0x7faa8eeb3d0f]

/usr/local/sage-8/local/lib/python2.7/site-packages/cysignals/signals.so(+0x9c3e)[0x7faa8eeb6c3e]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x128e0)[0x7faa8f2b68e0]

/lib/x86_64-linux-gnu/libc.so.6(__select+0x5f)[0x7faa8f038acf]

/usr/local/sage-8/local/lib/python2.7/lib-dynload/time.so(+0x1bce)[0x7faa8c2e8bce]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x843c)[0x7faa8f41a02c]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7b8)[0x7faa8f41b838]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7faa8f41ba49]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6e87)[0x7faa8f418a77]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7b8)[0x7faa8f41b838]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x624a)[0x7faa8f417e3a]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7b8)[0x7faa8f41b838]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x624a)[0x7faa8f417e3a]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7b8)[0x7faa8f41b838]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x624a)[0x7faa8f417e3a]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7b8)[0x7faa8f41b838]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x624a)[0x7faa8f417e3a]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7b8)[0x7faa8f41b838]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(+0x85c29)[0x7faa8f391c29]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7faa8f361ec3]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(+0x64c5c)[0x7faa8f370c5c]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7faa8f361ec3]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(+0xc56ea)[0x7faa8f3d16ea]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7faa8f361ec3]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3333)[0x7faa8f414f23]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7b8)[0x7faa8f41b838]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x624a)[0x7faa8f417e3a]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7e37)[0x7faa8f419a27]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7b8)[0x7faa8f41b838]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(+0x85c29)[0x7faa8f391c29]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7faa8f361ec3]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(+0x64c5c)[0x7faa8f370c5c]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7faa8f361ec3]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(+0xc5a02)[0x7faa8f3d1a02]

/usr/local/sage-8/local/lib/libpython2.7.so.1.0(+0xc1f7a)[0x7faa8f3cdf7a]