#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):
''Copied from the sage-release thread (slightly beautified):
''
1: {{{devel/sage/sage/graphs/generic_graph.py}}}
Doesn't terminate at all(?), gets killed even if I test just that
file, with {{{SAGE_TIMEOUT_LONG=3600}}} (1 hour)!
Testing with {{{-verbose}}}, I now experience the same doctest failure
John [Cremona]
reported (and only that):
{{{
...
Trying:
P = G.plot(save_pos=True, layout='spring')###line 11577:_sage_ >>>
P = G.plot(save_pos=True, layout='spring')
Expecting nothing
ok
Trying:
G.get_pos()###line 11581:_sage_ >>> G.get_pos()
Expecting:
{0: [1.17..., -0.855...],
1: [1.81..., -0.0990...],
2: [1.35..., 0.184...],
3: [1.51..., 0.644...],
4: [2.00..., -0.507...],
5: [0.597..., -0.236...],
6: [2.04..., 0.687...],
7: [1.46..., -0.473...],
8: [0.902..., 0.773...],
9: [2.48..., -0.119...]}
**********************************************************************
File
"/home/leif/sage-4.5.2.alpha0/devel/sage/sage/graphs/generic_graph.py",
line 8617, in __main__.example_191
Failed example:
G.get_pos()###line 11581:_sage_ >>> G.get_pos()
Expected:
{0: [1.17..., -0.855...],
1: [1.81..., -0.0990...],
2: [1.35..., 0.184...],
3: [1.51..., 0.644...],
4: [2.00..., -0.507...],
5: [0.597..., -0.236...],
6: [2.04..., 0.687...],
7: [1.46..., -0.473...],
8: [0.902..., 0.773...],
9: [2.48..., -0.119...]}
Got:
{0: [1.1644236010005358, -0.83686858657215979], 1:
[1.7943839700815074, -0.066920666682206337], 2: [1.2689961125613971,
0.14359096356381118], 3: [1.511860539628787, 0.59162048325984706], 4:
[1.9941403734258905, -0.53845815492480542], 5: [0.59110867097474395,
-0.2204272806589378], 6: [2.0144421480067041, 0.70158250822163282], 7:
[1.4603696336476519, -0.46717593533332896], 8: [0.90427280509063312,
0.79073173670301911], 9: [2.4603584159299983, -0.097675067576871527]}
Trying:
T = list(graphs.trees(Integer(7)))###line 11595:_sage_ >>> T =
list(graphs.trees(7))
Expecting nothing
ok
...
}}}
The following is the last output I get (note that the examples aren't
tested in order, i.e. original source line numbers usually aren't
monotonic):
{{{
Trying:
D.connected_component_containing_vertex(Integer(0))###line 3090:_sage_
>>> D.connected_component_containing_vertex(0)
Expecting:
[0, 1, 2, 3]
ok
Trying:
set_random_seed(0L)
Expecting nothing
ok
Trying:
change_warning_output(sys.stdout)
Expecting nothing
ok
Trying:
graphs.PetersenGraph().blocks_and_cut_vertices()###line 3117:_sage_
>>> graphs.PetersenGraph().blocks_and_cut_vertices()
Expecting:
([[6, 4, 9, 7, 5, 8, 3, 2, 1, 0]], [])
ok
Trying:
graphs.PathGraph(Integer(6)).blocks_and_cut_vertices()###line
3119:_sage_ >>> graphs.PathGraph(6).blocks_and_cut_vertices()
Expecting:
([[5, 4], [*** *** Error: TIMED OUT! PROCESS KILLED! *** ***
[3600.9 s]
----------------------------------------------------------------------
The following tests failed:
sage -t -long -verbose "devel/sage/sage/graphs/generic_graph.py" #
Time out
Total time for all tests: 3600.9 seconds
real 60m1.029s
user 0m2.360s
sys 0m0.884s
}}}
''[Note the real/CPU time.]''
The funny thing is that with {{{-verbose}}}, I do not even get the shell
prompt back (I redirected stderr to stdout and tee'd it); {{{./sage -t
-long ...}}} terminates, but I guess its now orphan child ({{{python
/home/leif/.sage//tmp/.doctest_generic_graph.py}}}[sic], which is actually
running - consuming CPU time, in contrast to its two {{{gap}}} children,
which sleep due to blocking reads) keeps at least one of the file
descriptors open...
''[This was on '''32-bit''' Ubuntu 9.04 (P4 Prescott 3.2GHz, gcc 4.3.3,
native code). John Cremona experienced the doctest failure on '''32-bit'''
SuSE...]''
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9584#comment:1>
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.
