Finding the problem in a doctest timeout

First time here? Check out the FAQ!

doctesting

Jason Bandlow
421 ●3 ●10 ●20

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?

add a comment

1 Answer

Sort by » oldest newest most voted

answered 14 years ago

mvngu
346 ●1 ●1 ●9

You 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.

link

Comments

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

Jason Bandlow ( 14 years ago )

add a comment

Your Answer

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

Add Answer

Question Tools

Stats

Asked: 14 years ago

Seen: 530 times

Last updated: Aug 19 '10

Finding the problem in a doctest timeout savecancel

1 Answer

Comments