#9584: Some graph-related doctest failures and timeouts with 4.5.2.alpha0
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: mvngu
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.5.2
Component: doctest | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by leif):
Replying to [comment:18 jhpalmieri]:
> I've set SAGE_TIMEOUT_LONG to 10000, and on both cleo and iras the test
is still timing out.
Wow... ;-) (Single test? Sysload?)
> On iras I ran it "verbose", and it stalled at this point:
{{{
Trying:
arborescences = g.edge_disjoint_spanning_trees(k)###line 3429:_sage_
>>> arborescences = g.edge_disjoint_spanning_trees(k)
Expecting nothing
}}}
> But that command works fine from the command line, and I'm not flushing
any buffers.
I don't think this is the point where it really starts hanging.
> Is it worth pursuing this further? If so, how should I modify
ncadoctest to flush buffers appropriately?
IMO yes; I've uploaded a patch to {{{ncadoctest.py}}} (which I think could
be merged into Sage anyway, since if at all it slows down only doctesting
in verbose mode).
Btw, you could look for Python and GAP orphans after the test has timed
out. (GAP processes should be the children of the orphaned Python doctest
process.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9584#comment:19>
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.
