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
do something about the pari overflow test #1595
Comments
comment:1
The issue has been added to the FAQ. It might be easiest to direct stderr to some file. That way people should never see the offending message. Cheers, Michael |
comment:3
On OSX 10.5 64 bit, FreeBSD 7 as well as Solaris Sparc this overflow test leads to a segfault/failed test. I am not sure what to do with this test since the fact that it worked purely depends on the OS behavior for large allocs. Maybe making it "optional -- large" or "optional -- $SOME_OS_LIST" would be a way out of this. Anyway, there seems to be no reliable way to test the allocation of huge amounts of memory and expect the Sage session to survive. Cheers, Michael |
comment:4
Attachment: gen.patch.gz |
comment:5
Positive review. Cheers, Michael |
comment:6
Oops, change the summary, too. Cheers, Michael |
comment:7
Ooops, this patch needs to be rebased for 3.4.1.rc1 - new patch coming up in the morning. Cheers, Michael |
comment:8
Attachment: trac_1595-rebase.patch.gz Merged trac_1595-rebase.patch in Sage 3.4.1.rc2. Cheers, Michael |
This disturbs people:
This would disturb people less:
Component: doctest coverage
Issue created by migration from https://trac.sagemath.org/ticket/1595
The text was updated successfully, but these errors were encountered: