Ask Your Question

Finding the problem in a doctest timeout

asked 2010-08-19 08:11:43 -0500

Jason Bandlow gravatar image

After changing a file and running the doctests, I'm getting:

sage -t  "devel/sage-trac/sage/combinat/sf/"
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***

 [360.2 s]
The following tests failed:

sage -t  "devel/sage-trac/sage/combinat/sf/" # 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?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2010-08-19 08:33:07 -0500

mvngu gravatar image

You could try running the doctest with the verbose option:

sage -t -verbose devel/sage-trac/sage/combinat/sf/ 2>&1 | tee -a doctest.log

Then look through the log file to find where the doctest timed out.

edit flag offensive delete link more


I had forgotten about 'verbose'. This is exactly what I was looking for. Thanks!

Jason Bandlow gravatar imageJason Bandlow ( 2010-08-19 08:44:56 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2010-08-19 08:11:43 -0500

Seen: 162 times

Last updated: Aug 19 '10