It is safe to build without setting SAGE_CHECK. Also, some packages are known to fail their test suites — see https://groups.google.com/d/msg/sage-devel/abysgIIVGZI/fF7efL9RAwAJ, for example.
On Saturday, January 11, 2020 at 2:40:04 AM UTC-8, Szabolcs Horvát wrote: > > Hello everyone, > > I tried to build Sage from source on macOS 10.14.6 / Xcode 11.3. Some > functionality, such as using CBC for integer programming problems, is only > supported if Sage is built from source. > > I set SAGE_CHECK="yes". Some of the tests seem to fail. > > I was wondering if others have managed to build Sage from source on this > platform and if the test suite passes for you. > > I cannot think of anything on my system that could have interfered with > the build. I do not have Homebrew. I have MacPorts and Anaconda Python, but > I removed both from the PATH environment variable before starting the build > (reverted PATH to a pristine value). > > I have attached the log files as instructed. > > > For cython, several tests appear to fail because of overflow errors with > long long. For example, > > Failed example: > long_long_abs(-max_long_long-1) #doctest: +ELLIPSIS > Expected: > Traceback (most recent call last): > ... > OverflowError: ... > Got: > -9223372036854775808 > > > For nose, the log file suggests that the tests are missing or not copied > to the final location? > > ValueError: Working directory 'build/tests' not found, or not a directory > Error running functional_tests. > > I could just not set SAGE_CHECK="yes" but is that safe? > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/95a5f5e1-d0da-48e4-97c4-df240780acd1%40googlegroups.com.
