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
Add an spkg-check file for Pari #9518
Comments
comment:1
Dave, I suggest that you leave this to be done as part of the #9343 upgrade. I have already started working on this, including reporting some issues with the testing script upstream to par-dev. I thought you would like this plan -- and pleasantly surprised to see that after fixing bugs they add tests to the suite. |
comment:2
Replying to @JohnCremona:
No problem. I actually get some failures. I'll attach the spkg-check file as an attachment, since I'd already done it. It will save you the hassle. I actually get some failures on my OpenSolaris machine. In fact, whilst Sage builds on OpenSolaris, it crashes at startup. So perhaps I might look at Pari as a possible source of trouble.
|
spkg-check for Pari |
comment:3
Attachment: spkg-check.gz I note there is an error in I leave you to sort that out!
|
comment:4
For an explanation of the errors see my post to pari-dev at http://pari.math.u-bordeaux.fr/archives/pari-dev-1007/threads.html and Karim's reply which I have not yet absorbed. I have been compiling pari and running its tests for about 20 years... |
This comment has been minimized.
This comment has been minimized.
comment:7
There is an spkg-check in #9343 and it seems to work, so positive review. |
John Cremona remarked on #9281 that Pari had a self test that could be run from
make test-all
, so an spkg-check file should be added to do this. I will take care of it. Hopefully John can review it.Dave
Marked "duplicate/invalid/wontfix" because it is now in #9343. -- Jeroen Demeyer
CC: @JohnCremona @williamstein @robertwb
Component: spkg-check
Issue created by migration from https://trac.sagemath.org/ticket/9518
The text was updated successfully, but these errors were encountered: