New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failures of Python (2.6.4.p9) on OpenSolaris x64 (64-bit) #9299
Comments
This comment has been minimized.
This comment has been minimized.
Changed keywords from none to testsuite, Python modules, Failed, SAGE_CHECK |
comment:2
Python testsuite failures are not specific to OpenSolaris (I've seen them on Ubuntu 9.04, too). |
comment:3
Replying to @nexttime:
Yes, but the tests which actually fail vary from system to system, with the exception of Dave |
comment:8
obsolete ? |
Reviewer: Matthias Koeppe |
Although Sage 4.4.4.alpha1 does not build on OpenSolaris x64, the standard Python package does.
Build environment
The background
Although Sage 4.4.4.alpha1 (or any Sage version for that matter) does not build fully on OpenSolaris, the Python module does build fully. However, unless #9041 is applied, _socket will not build which prevents several parts of Sage from building.
Furthermore, unless #9295 is applied, exporting SAGE_CHECK to "yes" will not result in any tests of the Python package.
Summary of test results
Here are the summary of the test results. Although there are the same number of failures as observed on Solaris 10 SPARC (32-bit), the failures are not always the same - there are some unique to OpenSolaris and some unique to Solaris 10. See #9297 for the Solaris 10 SPARC (32-bit) failures of Python.
Individual test failures
On failure seems a little strange below, where it reports "not enough space". The machine has 990 GB of free space!
CC: @jaapspies @nexttime @mkoeppe
Component: porting: Solaris
Keywords: testsuite, Python modules, Failed, SAGE_CHECK
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/9299
The text was updated successfully, but these errors were encountered: