-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
update pari to 2.15.4, drop patch #35302
Conversation
I updated it in ::gentoo. The changelog looks safe but I haven't run the sage test suite yet. The "Build & Test" CI has a green checkmark but looks like it crashed to me? |
What has crashed? |
It also won't let me upload a screenshot. The raw logs look OK, it's only the summary that's busted. |
On the topic of patching PARI, please have a look at #35219. |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #35302 +/- ##
===========================================
- Coverage 88.62% 88.60% -0.02%
===========================================
Files 2148 2148
Lines 398855 398855
===========================================
- Hits 353480 353409 -71
- Misses 45375 45446 +71
... and 28 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
And indeed doesn't start with stacksize 10kb:
|
works for me, e.g. on macOS:
and on GitHub's CI. |
OK, reproducible on Fedora, |
Upstream patch is now available at #2469. (Is there any way for me to push to this branch?) |
everyone can open a PR against the branch of this PR, irrespective of any team membership. I.e. go to my fork and open a PR there, against the correct base. |
I've left tests in (2 new tests in sagelib, and 2 tests in spkg-configure.m4) |
Please review |
### 📚 Description update pari to 2.15.4, drop patch Will fix sagemath#35219 ### 📝 Checklist - [x] I have made sure that the title is self-explanatory and the description concisely explains the PR. URL: sagemath#35302 Reported by: Dima Pasechnik Reviewer(s): Dima Pasechnik, Lorenz Panny, Michael Orlitzky
I'm getting a lot of
random, but on half of the buildbots |
Also get it without this, probably something else that randomly increases the failure probability. |
### 📚 Description update pari to 2.15.4, drop patch Will fix sagemath#35219 ### 📝 Checklist - [x] I have made sure that the title is self-explanatory and the description concisely explains the PR. URL: sagemath#35302 Reported by: Dima Pasechnik Reviewer(s): Dima Pasechnik, Lorenz Panny, Michael Orlitzky
I recently removed sign_on/off from a piece of code which was calling plain Python. PR #??? (sorry, afk). |
FWIW, I've been on pari 2.15.3 since march and pari 2.15.4 since july, without any regressions. Ofc these kind of bugs tend to appear on very heavy loaded boxes. The fact that now appears more often might also be related to the boxes now being more loaded. |
this might be related to cypari2 memory model being very suboptimal, creating reference counted Python objects for everything Pari puts on the stack. see #32360 (comment) |
### 📚 Description update pari to 2.15.4, drop patch Will fix sagemath#35219 ### 📝 Checklist - [x] I have made sure that the title is self-explanatory and the description concisely explains the PR. URL: sagemath#35302 Reported by: Dima Pasechnik Reviewer(s): Dima Pasechnik, Lorenz Panny, Michael Orlitzky
OS X does not have a command
finishes in well under 1 second on my machine, printing "ok":
|
Some untested options for OS X: https://unix.stackexchange.com/a/43346, https://unix.stackexchange.com/a/18711, https://stackoverflow.com/a/35512328/1401572. |
We already have a version test near the top of pari's I have always thought this was a waste of time, but since in this case it was someone else's time, who am I to complain :) But what I'm getting at is that maybe now we should just bump the main version requirement up to 2.15.4. Anyone who would've packaged such a FrankenPARI-2.15.3 will most certainly have upgraded to 2.15.4 by now. Then the two bug tests (and in particular, the |
|
Or the logic could be: if you're using anything older than 2.15.4, run those particular tests, but skip those tests with 2.15.4 or later. Or at least do this with the one test that uses I don't really have an opinion about how to solve it, I would just like a solution that lets me use homebrew's pari:
and
|
bumping the lower bound in #36732 |
📚 Description
update pari to 2.15.4, drop patch
Will fix #35219
📝 Checklist