On Sep 24, 6:02 pm, "Andrzej Giniewicz" <[EMAIL PROTECTED]> wrote: > Built fine, tested fine with one non-repeatable so far "time-out", in > plot.py - seems time-out is also reason for 2 failures mentioned on > that 32bit fedora... (looking at that version that passed, 335 seconds > is quite some)...
ok, good that it works, somewhat bad that it times out. > is there already command-line option to set longer times on slower > machines? Also, is the time counted per "sage: ..." line or whole > file? I think the "per-line" approach if possible could give a chance > to give "All tests passed" on slower machines also while detecting > hang on faster machines too, so if it is per-file, is it good idea to > reset the timer every one test case? There is no command line option, but we could use an environment variable. But the proper fix would be that when doctesting sage should roughly determine the speed of the machine and adjust the timeout value for slower boxen. > cheers, > Andrzej. Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
