-
-
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
Upgrade: pari 2.13 #30801
Comments
comment:2
This needs first a new cypari release including sagemath/cypari2@1a4be24, otherwise it crashes immediately. After that, things don't look good:
|
comment:3
The timeouts are hangs when calling nffactor. A minimal test case:
I've bisected it to upstream commit [1], but running the same code directly in gp works fine. |
comment:5
So, the actual issue seems to be:
If I set primelimit to 0 in gp I can reproduce the hangs. Reported to cypari sagemath/cypari2#96 |
comment:6
Another issue is the return of:
returns:
but configure expects |
comment:7
ok, they changed the output format. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Author: Vincent Delecroix |
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:13
Many test failures are caused by pari having changed the normal Smith form algorithm, which now gives different transition matrices. Most of them are still correct, but it also has some unfortunate side effects:
|
This comment has been minimized.
This comment has been minimized.
comment:15
On Tuesday (November 3) from 14h to 17h (UTC+2) there is a virtual PARI/GP workshop. I intend to discuss with Bill the cypari2 release and the adaptation in SageMath. Anybody interested is more than welcome. Just send me a private e-mail so that I can forward the announcement. |
comment:16
The update to cypari 2.1.2b causes some additional issues (not present in 2.1.1, both tested with pari 2.13)
|
comment:17
This is the problematic line
Some of these poldegree are "corrected" in commit 5358fc2. I see several solutions
|
comment:18
To my mind, fixing Sage |
comment:19
Related: the functions
|
comment:20
See #30849 |
Dependencies: #30849 |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:22
(Rebased on top of #30849 dropping modification to gcd/lcm when poldegree is involved) |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:188
Confirming this branch eliminates the error I was seeing in PARI/GP's qfminim(), due to a bug in PARI/GP that's since been corrected in that libraries source code. My elliptic curve code is now running properly again. New commits:
|
comment:189
This had a positive review before the issues with local components came up, and I'm confident those are fixed, so I think we can reinstate the positive review. |
Changed reviewer from Dima Pasechnik to Dima Pasechnik, David Loeffler |
Changed branch from public/30801 to |
Changed commit from |
comment:192
With 9.4.b3 and pari 2.13, my patchbot petitbonum has now two errors in src/sage/modules/fg_pid/fgp_module.py |
comment:193
Replying to @fchapoton:
is it the same as in comment:178 ? |
comment:194
yes, exactly the same as comment:178, see |
comment:195
Right, I see, it actually depends upon the random seed.
on the same machine, but with Sage built using clang 10, with 0 random seed these tests pass.
I suppose this should become part of #29935 |
comment:196
I believe this will be fixed with #29978. |
comment:197
No, #29978 does not fix the problem. |
comment:198
I see. I got confused. So there is actually 2 failing doctests in lines 1274 and lines 1294 that should be fixed. |
comment:199
Replying to @kliem:
#29978 fixes the clang setup from comment:195 fully, but the gcc (gcc version 10.3.1 20210422 (Red Hat 10.3.1-1)) Maybe it's a gcc 10 bug? Or we have randomness in various Sage packages not fully under control, otherwise this discrepancy looks strange. |
comment:200
I think the fix is quite trivial. Apparently with |
comment:201
See #32048 for a possible fix. |
comment:202
The problem above and another error not reported before, are responsible for "my" patchbot panke to be dead for now, I just found out.
I don't know why you introduced set in a doctest. It's not stable. In #29977 I try to fix it by just outputing |
comment:203
the Python's insane treatment of sets makes me mentally unstable, this is for sure. |
comment:204
sorry for screaming... |
comment:205
Perhaps
How about using |
comment:206
Doctests try to sort dictionaries and sets uniquely. However it fails here. This is really strange. It apparently depends on the compiler(?):
on Debian buster with pari 2.13.1 installed and gcc 8.3.
on Ubuntu focal with pari 2.13.1 installed and gcc 9.3.0. The problems is that the output is not sortable:
Hence ipythons pretty printer fails https://github.com/ipython/ipython/blob/master/IPython/lib/pretty.py. |
comment:207
Let's move the discussion to #29977. |
This is to upgrade to PARI 2.13.x. https://repology.org/project/pari/versions
This new PARI release brings a lot of bug fixes,
new functionality, and speedups.
Changes in the PARI library that needs adaptation in SageMath code
Last upgrade:
Follow-up ticket: #31754
Upstream: Fixed upstream, but not in a stable release.
CC: @dimpase @orlitzky @mkoeppe @slel @antonio-rojas @kiwifb @videlec @tobihan @collares @isuruf @dkwo @xcaruso @loefflerd @kliem
Component: packages: standard
Keywords: upgrade, pari
Author: Vincent Delecroix, Antonio Rojas, Gonzalo Tornaría
Branch:
c78b147
Reviewer: Dima Pasechnik, David Loeffler
Issue created by migration from https://trac.sagemath.org/ticket/30801
The text was updated successfully, but these errors were encountered: