On 09/18/2010 02:10 PM, Robert Bradshaw wrote: > On Sat, Sep 18, 2010 at 6:17 AM, Niles <nil...@gmail.com> wrote: >> but the test only runs on sage.math, so is it only a bug on >> sage.math? > > Well, that was a lot easier than having some kind of system > calibration in place for all other computers...
We *could* try a variation on William's timeit.test: http://groups.google.com/group/sage-devel/browse_thread/thread/c97d36d23131f4c5/dc3db8fc866211bb?#dc3db8fc866211bb David Kirkby has suggested at #8254 http://trac.sagemath.org/sage_trac/ticket/8254 that disk/filesystem speeds are more important than CPU speeds here. >> I think the trac server is the place where bugs are >> properly acknowledged anyway. If adding a failing doctest to sage is >> the way to get a bug recognized, I'm sure we can all send in our >> favorites. > > It's a regression test. Sage took way to long to start up, so we did a > lot of work to (partially at least) fix it, and we added a test to > make sure the startup time didn't get to long again (which it looks > like it has). This wasn't a failing test when we added it. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
