-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Further clean-up of expect.py #17718
Comments
Branch: u/jdemeyer/ticket/17718 |
Commit: |
comment:3
Why
If this is necessary, could you add a doctest? |
comment:4
Replying to @videlec:
It's to allow So it's covered by this doctest change: -sage: with StdOutContext(gp):
-... gp('1+1')
-...
+sage: with StdOutContext(Gp()) as g:
+....: g('1+1') |
Changed branch from u/jdemeyer/ticket/17718 to u/mmezzarobba/17718-expect |
comment:6
Why that extra commit? |
comment:7
Replying to @jdemeyer:
As the commit message says: to make the optional test involving octave pass also when the tests are run with |
comment:8
Replying to @mezzarobba:
I'm not aware of any general rule that tests should pass when run with |
comment:9
In any case, this could be discussed in a different ticket. |
Changed branch from u/mmezzarobba/17718-expect to u/jdemeyer/ticket/17718 |
comment:10
Replying to @jdemeyer:
What is the point of having an option
I agree in principle, but here I don't think the example without its Anyway, I'm fine with leaving that change out if you prefer. |
Reviewer: Vincent Delecroix, Marc Mezzarobba |
comment:11
This leads to random failures in the R interface on my desktop (Haswell-E Linux x86_64, background computation running)
|
comment:12
another failed example (seems to be falling over a prompt in the R docs if you are unlucky with the timing):
pexpect log:
|
comment:13
Replying to @vbraun:
Are you really sure that this is caused by this ticket? The point is that this ticket is really a clean-up ticket, with almost no functional changes. |
comment:14
Well maybe it triggers a pre-existing bug. All I know for sure is that doctests get stuck in R on my machine with it. |
comment:15
How common is this failure? |
comment:16
Maybe 50% when the system is under load... |
comment:17
When I have some time, I'll try to reproduce it. The only possible reason that I can think of is the change If that's the cause, I suggest to just revert that. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:19
I confirm the issue and this should fix it. |
comment:20
Patchbot says fine. Tests in |
Changed reviewer from Vincent Delecroix, Marc Mezzarobba to Vincent Delecroix, Marc Mezzarobba, Ralf Stephan |
Changed branch from u/jdemeyer/ticket/17718 to |
Depends on #17704
Component: interfaces
Author: Jeroen Demeyer
Branch/Commit:
c8d1a28
Reviewer: Vincent Delecroix, Marc Mezzarobba, Ralf Stephan
Issue created by migration from https://trac.sagemath.org/ticket/17718
The text was updated successfully, but these errors were encountered: