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
timeouts in doctests on OS X 10.9 #16474
Comments
comment:2
even after reverting the corresponding commit from #15631 I still get lots of doctest timeouts. |
comment:3
I'm not suggesting this as a fix (because I don't know anything about the pexpect interface), but if I make this one change: diff --git a/src/sage/interfaces/singular.py b/src/sage/interfaces/singular.py
index 576fcc7..97ed05d 100644
--- a/src/sage/interfaces/singular.py
+++ b/src/sage/interfaces/singular.py
@@ -378,7 +378,7 @@ class Singular(Expect):
"""
prompt = '> '
Expect.__init__(self,
- terminal_echo=False,
+ terminal_echo=True,
name = 'singular',
prompt = prompt,
command = "Singular -t --ticks-per-sec 1000", #no tty and fine grained cputime() then I don't get the timeouts any more. (I get other doctest failures because of this, but no timeouts.) |
comment:4
in case, note #16260#comment:62 |
comment:5
I've debugged the issue on OSX 10.9 and when the hang happens
One way to reduce the likelihood of the hang is to insert a sleep before first reading from the subproces (in |
This comment has been minimized.
This comment has been minimized.
comment:6
Sleeping 100ms when starting Singular reduces the failure rate in |
comment:8
The branch attached is obviously a no-op, and just moves the setecho(0) further down after we read the first prompt. But it seems to improve things in my limited testing. New commits:
|
Author: Volker Braun |
Commit: |
comment:9
This seems to fix it, I haven't seen another failure in |
comment:10
Oh, very nice. This fixes it on two OS X 10.9 machines. |
Reviewer: John Palmieri |
Changed branch from u/vbraun/timeouts_in_doctests_on_os_x_10_9 to |
There are frequent timeouts when doctesting on OS X with pexpect interfaces, in particular Singular. For example:
These became much more frequent by the changes in the Singular/pexpect interface from #15631 on two buildbots:
Other build bots do not seem to be affected, so its a likely pty kernel bug.
CC: @vbraun
Component: interfaces
Author: Volker Braun
Branch/Commit:
2928b9a
Reviewer: John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/16474
The text was updated successfully, but these errors were encountered: