#12415: Update doctesting framework
---------------------------------------------------------------------------------------------------------------------------------+
Reporter: robertwb
| Owner: mvngu
Type: enhancement
| Status: needs_review
Priority: major
| Milestone: sage-5.3
Component: doctest
| Resolution:
Keywords:
| Work issues:
Report Upstream: N/A
| Reviewers: Jeroen
Demeyer
Authors: David Roe, Robert Bradshaw
| Merged in:
Dependencies: #13147,#13146, #13145, #12723, #12392, #12393, #12395,
#12396, #12397, #12381, #12382, #12383, #12384, #11871 | Stopgaps:
---------------------------------------------------------------------------------------------------------------------------------+
Changes (by roed):
* status: needs_work => needs_review
Comment:
I thought I'd solved the sporadic problem in sage.tests.interrupt by
increasing the delays in `test_sig_block_outside_sig_on`: after the change
I ran `sage -tp --sagenb --long devel/sage/doc/common
devel/sage/doc/[a-z][a-z] devel/sage/sage` 10 times with no failures
(where before there had been 5 failures in `interrupt.pyx`). But I just
got another one. Maybe it has to do with the load on sage.math? There
are more processes running now than when I ran the test earlier.
Jeroen, would you be willing to take a look at it since you wrote the
tests in that file?
All the other tests pass for me, with the exception of startup.py.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12415#comment:94>
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.
