Something like that. Each test file contains a record of how long the entire file takes in units proportional to how long a specific test file takes. I believe the constant is currently chosen so that 1 unit corresponds to 1msec on a 1ghz pentium class processor.
The standard test suite runs the tests from fastest to slowest and gives estimates on how long the test will take on the current computer based on the recorded timings versus the actual timings of the previous tests. This has proven adequate to detect several slowdowns in development code before it was released and also provide a friendly progress meter to those not using supercomputers. On Aug 10, 4:10 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On 8/10/07, Jack Schmidt <[EMAIL PROTECTED]> wrote: > > > > > You might look at how GAP does this. Its tst directory contains > > expected timings. One only compares relative times. GAP tests do not > > fail on a pentium 75mhz, since GAP users employ a wide range of > > hardware. Surely other software has similar features. > > So you're suggesting something like: > > sage: 2 + 2 # takes at most 5s on a 2Ghz processor > > -- 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
