One solution with long doctest is to (optionally) flag them with a time
indication
# long 30sec
# long 1min
# long 1hour
# long 3year
Then, when testing we could add an option to skip the one which are too
long for our purpose
sage -t --all --skip-longer-than 2min
And I think that the default could reasonably be 10sec.
On 03/11/15 17:16, Jori Mäntysalo wrote:
On Tue, 3 Nov 2015, John Cremona wrote:
I agree. There are test runs which take an hour (say, just for the
sake of argument) which I like to know still work -- or to see if
after some other changes they now only take half an hour -- but that
it much too long for a "long time" test.
That will be a problem if you, for example, decide to become a reindeer
farmer, move to Lapland and stop making software. Local test files will
then be forgotten.
http://doc.sagemath.org/html/en/developer/coding_basics.html says "Skip
all doctests of a file/directory file: If one of the first 10 lines of a
file starts with any of r""" nodoctest - -". So can we just add those
extra tests to files marked with that?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
