On Wed, Apr 23, 2008 at 10:35 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Apr 24, 1:54 am, Bjake Hammersholt Roune <[EMAIL PROTECTED]> > wrote: > > Hi Bjake, > > > > It just now occured to me that this might be due to counting wall-time > > instead of CPU-time, since I put the machine to sleep during a lecture > > while it was running the tests. > > Ok, that explains it. On OSX time prints the time elapsed [at least > per default] while on Linux it actually prints the CPU time used. I > guess this boils down to BSD vs. GNU default behavior. Should we > actually fix this? If somebody thinks so please open a ticket and > mention the fact here.
The code (in local/bin/sage-*test*) that times out the testing of a file uses walltime instead of cputime. That's the code that led to the error the user observed. This is the only reasonable thing to do, because the file being doctested can involve long calls to separate subprocesses. -- William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
