-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
fix a calculus doctest (giac, laplace, integration) #22833
Comments
Branch: u/chapoton/22833 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
Reviewer: Travis Scrimshaw |
comment:3
I thought someone had already fixed this, but I guess not. |
comment:4
the error was because of the double |
comment:5
The change to TESTS:: was just something I could not keep like that once I had seen it. I am not sure that the change to integration doctest is ok. If it fails on your machine, then you can set this ticket back to needs work. |
comment:6
failing in my machine with:
|
comment:7
The first failure is not a true failure and is independent. We need to figure out what makes this test pass on some systems and not on others. |
This comment has been minimized.
This comment has been minimized.
comment:9
I see this failure with giac 1.2.3. The branch works for me. This problem is rather annoying, it prevents my patchbot from giving any green light.. |
comment:10
@mforets, could you try the following, please:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:13
And also tell me what you get when doing
|
comment:14
Replying to @fchapoton:
EDIT: no no, ignore my last message, I hadn't notice that you pushed changes < 1hr ago. i've recompiled this branch and i'm getting:
|
comment:15
in my machine, and for the commit 79442f3, i have
and i still get:
this exception is raised when we transform back to sage. maybe it's better to mimick the unevaluated laplace as with the SymPy case, that is:
i git pulled and re-compiled everything, so i ignore why you get "integration" instead. that said, if you have pressing need then you may as well consider removing this "no-go" test altogether.. |
comment:16
Replying to @mforets:
with that modif, the expected output for the test at hand becomes: in my machine the updated code passes. let me know if you want me to push that or try something else. |
comment:29
Also, do you have
|
comment:30
in symbol_table['functions'] and
|
comment:31
That's the difference: I don't have the |
comment:32
|
comment:33
Sorry, I was vague, I meant:
|
comment:34
|
comment:35
|
comment:36
Now I'm not so sure about what to look for or ask, but I'm investigating. Ralf, do you have any ideas? |
comment:37
So I think what is happening is that |
comment:38
does this pass?
|
comment:39
Let me try to summarize. We cannot fix the doctest because of conflicting results due to giac's clever use of locale which breaks its interface to the world. The immediate way to adapt to this IMO is to look for both |
comment:40
could somebody please take action here, and propose a better branch ? |
comment:41
What is the desired output of
If it is
to
Without the change the doctest would pass but with the change I get
|
comment:42
again, for consistency the desired output of from your answers, i can reproduce the issue playing with hence, let me upload a branch doing rws's comment:39 and my comment:38, if i understood correctly. |
New commits:
|
Changed author from Frédéric Chapoton to Frédéric Chapoton, Marcelo Forets |
Changed branch from u/chapoton/22833 to u/mforets/22833 |
comment:44
Just to confirm that merging this branch in Sage 8.0.beta6 fixes the doctest error on my system. |
Changed reviewer from Travis Scrimshaw to Travis Scrimshaw, Steven Trogdon |
comment:45
I think this is good. |
Changed branch from u/mforets/22833 to |
that currently prevents many patchbots to run smoothly
CC: @rwst @frederichan-IMJPRG
Component: calculus
Author: Frédéric Chapoton, Marcelo Forets
Branch/Commit:
e2d74c6
Reviewer: Travis Scrimshaw, Steven Trogdon
Issue created by migration from https://trac.sagemath.org/ticket/22833
The text was updated successfully, but these errors were encountered: