-
-
Notifications
You must be signed in to change notification settings - Fork 572
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 to Singular-3-1-7p1 #17184
Comments
Branch: u/jdemeyer/ticket/17184 |
Commit: |
comment:2
boxen is down, cannot test... New commits:
|
comment:3
One thing I actually did not test because i just forgot: check that it still builds with SAGE_DEBUG as it is quite involved for Singular. |
comment:4
Boxen is back up (from here at least)! |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
That's a lot of dropped patches. That, on its own, would justify the upgrade. |
comment:7
Needs some work for the debug version. |
Changed branch from u/jdemeyer/ticket/17184 to u/jpflori/ticket/17184 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:11
Without the latest debug patches, without
|
comment:12
I get these doctest failures also with the latest version of this ticket, without NTL. |
comment:14
I don't really remember who committed the "my_awesome_ring" code. |
comment:15
Looking at the failing example in
|
comment:16
Wasn't me, but if there were any changes to the genus function then hopefully they fix #15477 |
comment:17
When the
|
comment:18
And this is the new piece of code in 3-1-7 in iplib.cc around line 453:
In fact the whole block (not only the one included above) used to be around line 556 in 3-1-6. |
comment:19
In that very piece of code, Singular 4-0-1 and 3-1-7 look similar, so we might face this issue even if going for 4-0-1 directly... |
comment:20
Groumpf, I don't remmeber if anyone from the Singualr team has an account here on trac... |
comment:50
I'll give it a shot, but as Singular is a standalone process I need some dark magic to attach gdb to it and debug it. |
comment:51
Backtrace:
|
comment:52
Run with |
comment:53
Thanks a lot for the pointer.
And on relaunch:
|
comment:54
Ok, the issue is that |
comment:55
It seems Singular 3-1-6 was more careful:
|
comment:56
Looks like an upstream bug, did you post it there? |
comment:57
Not yet, still investigating, it seems the following change (here reversed) between 3-1-6 and 3-1-7 may be the issue:
|
comment:58
For future ref the change was part of Singular commit: |
comment:59
Upstream report at: And removing the "#if 0" makes the simple test pass. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:61
Things look fine for me except for timeouts which I already got before in debug mode, and two spurious errors I can not reproduce. |
comment:62
Fails on OSX with (this is a fresh install):
and more like that, see http://build.sagedev.org/release/builders/%20%20fast%20Volker%20MiniMac%20%28OSX%2010.10%20x86_64%29%20full/builds/0/steps/compile_1/logs/singular |
comment:63
Can you try without |
comment:64
Anyway, I don't see any use of the instantiated NTL classes within the |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from u/jpflori/ticket/17184 to |
Singular 3-1-7p1 repackaged (see spkg-src):
CC: @vbraun @nbruin @burcin
Component: packages: standard
Author: Jean-Pierre Flori
Branch/Commit:
4e287c4
Reviewer: Volker Braun
Issue created by migration from https://trac.sagemath.org/ticket/17184
The text was updated successfully, but these errors were encountered: