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. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
