-
-
Notifications
You must be signed in to change notification settings - Fork 488
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 pynac-0.7.13 #24262
Comments
Branch: u/rws/upgrade_to_pynac_0_7_13 |
New commits:
|
Commit: |
comment:3
No doctests need to be adapted for this release. Please review. |
comment:4
On Debian 8.1.rc2 + #24240, compiles without difficulty.
The simplifications are not fixed either (but I'm not sure they could be by pynac's upgrade...) :
==> |
Reviewer: Emmanuel Charpentier |
comment:5
Replying to @EmmanuelCharpentier:
They are always added in the reporting tickets.
They need to be fixed by updating Flint, as I have submitted the fix to Flint some time ago.
Sorry but you didn't report that. Of course I'll add it soon.
I have pointed out already that
Well, see #24176.
This is a Pynac build enhancement.
Done.
What do you mean with "non-transient"? "non-transient using make ptestlong" or "non-transient using sage -t manually"? I cannot reproduce using sage -t on OpenSuSE, so this might be system-specific, or it might be make ptestlong-specific. |
Author: Ralf Stephan |
comment:7
Replying to @rwst:
[ Snip... ]}
I just did that. |
comment:8
Replying to @rwst:
[ Snip... ]
I get the failure during
|
comment:9
Confirmed with |
comment:10
Okay the reason is a regression in |
comment:11
Replying to @rwst:
Hmmm... This a catastrophic one : |
comment:12
A blocker is a ticket that reports/fixes an existing bug in Sage. This is a ticket that potentially introduces a severe bug, but with the right patch, it becomes a normal ticket. The sky does not fall down. |
comment:13
Replying to @rwst:
Ah ! You meant that this regression was introduced by the upgrade to pynac ? That was not obvious (at least to me...) ; I thought that you have found a pre-existing regression. And that was deserving a blocker ticket. |
comment:15
This fixes the issue. My ptestlong passes but you might want to test again too. Note that the behaviour of this added doctest:
is unchanged with respect to previous Sage versions but I have opened a Pynac issue: pynac/pynac#287 |
comment:16
Doesn't smell good.. On top of 8.0.rc3+#24240, I get :
These errors don't seem to be cosmetic (i. e. space, printing order, etc...).
Sorry... |
comment:17
Replying to @EmmanuelCharpentier:
[ Snip... ]
Definitely |
comment:18
It doesn't look like you updated your copy of the ticket branch, e.g.. git trac pull.24262. |
comment:19
Replying to @rwst:
From the top of my git log :
I don't understand it, either... |
comment:20
The usual gotcha: I forgot to bump the patchlevel, so Pynac was not recompiled when you started |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:23
Smells better :
|
comment:24
On top of 8.0.rc3+#24240, passes ==> |
comment:25
Merge conflict |
comment:26
We might as well upgrade to 0.7.14 in one go. I'll prepare #24329 as soon as 8.2.beta1 is out. |
comment:27
Duplicate of #24329. |
There is:
ex.coefficients()
bugs (Doctest: segmentation fault with coefficients() on symbolic expressions #23545, Segfault with ex.coefficients #24147)asin
/atan
enhancements (Some trivial identities and simplifications missed by Sage (pynac ?) #24211)set_of_all()
function (ConditionSet, ImageSet: Implement formal Set comprehension #24176)ax_cxx_compile_stdcxx_11.m4
https://github.com/pynac/pynac/releases/download/pynac-0.7.13/pynac-0.7.13.tar.bz2
CC: @kiwifb
Component: packages: standard
Author: Ralf Stephan
Branch/Commit: u/rws/upgrade_to_pynac_0_7_13 @
438816e
Reviewer: Emmanuel Charpentier
Issue created by migration from https://trac.sagemath.org/ticket/24262
The text was updated successfully, but these errors were encountered: