#13437: Clean up SIGALRM handling in p_iter_fork
-------------------------------+--------------------------------------------
Reporter: nbruin | Owner: tbd
Type: defect | Status: new
Priority: minor | Milestone: sage-5.4
Component: performance | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by SimonKing):
Replying to [comment:9 jdemeyer]:
> Is there any reason to assume that these 3 failures are related? Since
the doctest failures are in different files, I would guess that we're
seeing 3 different bugs.
I can't tell. I have no access to a machine where these errors occur,
nobody has ever produced a backtrace of it, and I even don't know in what
test in each file the error occurs, what happens with gdb, what happens
verbose, etc.
The three errors just "look" the same, in the sense of the doctester
reports the same problem. That's why I think that the underlying problem
could be the same.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13437#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
