Dear John, On 5 Jul., 21:22, John H Palmieri <[email protected]> wrote: > > - How can one influence the time after which a test is killed? > > Look at the file SAGE_ROOT/local/bin/sage-doctest: it uses environment > variables SAGE_TIMEOUT and SAGE_TIMEOUT_LONG to determine how long (in > seconds) to test with 'sage -t' and 'sage -t -long' respectively. So > adjust those variables before running sage -t.
OK, this was one of the things I was looking for. Does the given timeout concern the computation time for a single command or is it the total time for all tests in a file? > > - How can I find out what test caused the time out? > > Try 'sage -t -verbose FILENAME'. Does that do what you want? By miracle, the timout disappeared. Helas. But I tested the -verbose option, and it indeed seems to be what I was looking for. So, there only remains the question about a reasonable length of a test suite, and the questions on the role of spkg-check (used by whom and when? expected output?) that I asked in a different thread. Thank you very much! Simon --~--~---------~--~----~------------~-------~--~----~ 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-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
