ASKSAGE: Sage Q&A Forum - Individual question feedhttp://ask.sagemath.org/questions/Q&A Forum for SageenCopyright Sage, 2010. Some rights reserved under creative commons license.Thu, 19 Aug 2010 08:44:56 -0500Finding the problem in a doctest timeouthttp://ask.sagemath.org/question/7592/finding-the-problem-in-a-doctest-timeout/After changing a file and running the doctests, I'm getting:
sage -t "devel/sage-trac/sage/combinat/sf/hall_littlewood.py"
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***
[360.2 s]
----------------------------------------------------------------------
The following tests failed:
sage -t "devel/sage-trac/sage/combinat/sf/hall_littlewood.py" # Time out
Total time for all tests: 360.3 seconds
Is there an easy way to find out which test it was running when the timeout occurred? Or, equivalently, which tests did pass successfully?Thu, 19 Aug 2010 08:11:43 -0500http://ask.sagemath.org/question/7592/finding-the-problem-in-a-doctest-timeout/Answer by mvngu for <p>After changing a file and running the doctests, I'm getting:</p>
<pre><code>sage -t "devel/sage-trac/sage/combinat/sf/hall_littlewood.py"
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***
[360.2 s]
----------------------------------------------------------------------
The following tests failed:
sage -t "devel/sage-trac/sage/combinat/sf/hall_littlewood.py" # Time out
Total time for all tests: 360.3 seconds
</code></pre>
<p>Is there an easy way to find out which test it was running when the timeout occurred? Or, equivalently, which tests did pass successfully?</p>
http://ask.sagemath.org/question/7592/finding-the-problem-in-a-doctest-timeout/?answer=11430#post-id-11430You could try running the doctest with the verbose option:
sage -t -verbose devel/sage-trac/sage/combinat/sf/hall_littlewood.py 2>&1 | tee -a doctest.log
Then look through the log file to find where the doctest timed out.Thu, 19 Aug 2010 08:33:07 -0500http://ask.sagemath.org/question/7592/finding-the-problem-in-a-doctest-timeout/?answer=11430#post-id-11430Comment by Jason Bandlow for <p>You could try running the doctest with the verbose option:</p>
<pre><code>sage -t -verbose devel/sage-trac/sage/combinat/sf/hall_littlewood.py 2>&1 | tee -a doctest.log
</code></pre>
<p>Then look through the log file to find where the doctest timed out.</p>
http://ask.sagemath.org/question/7592/finding-the-problem-in-a-doctest-timeout/?comment=23056#post-id-23056I had forgotten about 'verbose'. This is exactly what I was looking for. Thanks!Thu, 19 Aug 2010 08:44:56 -0500http://ask.sagemath.org/question/7592/finding-the-problem-in-a-doctest-timeout/?comment=23056#post-id-23056Answer by ccanonc for <p>After changing a file and running the doctests, I'm getting:</p>
<pre><code>sage -t "devel/sage-trac/sage/combinat/sf/hall_littlewood.py"
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***
[360.2 s]
----------------------------------------------------------------------
The following tests failed:
sage -t "devel/sage-trac/sage/combinat/sf/hall_littlewood.py" # Time out
Total time for all tests: 360.3 seconds
</code></pre>
<p>Is there an easy way to find out which test it was running when the timeout occurred? Or, equivalently, which tests did pass successfully?</p>
http://ask.sagemath.org/question/7592/finding-the-problem-in-a-doctest-timeout/?answer=11441#post-id-11441Would it help to run with gdb attached? It's one of the advanced options listed from ./sage -advanced
"
-gdb -- run Sage under the control of gdb
-gdb-ipython -- run Sage's Ipython under the control of gdb
"
Perhaps then you could pause execution before the timeout, or perhaps try some sort of profiling?
This is only a guess, please be gentle. =)Thu, 19 Aug 2010 08:38:02 -0500http://ask.sagemath.org/question/7592/finding-the-problem-in-a-doctest-timeout/?answer=11441#post-id-11441