On Fri, Sep 17, 2010 at 2:22 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2010-09-17 11:08, Mike Hansen wrote: >> Or, an alternative to just removing the test is to make it so that >> Sage starts up faster so that the test doesn't fail. Something like >> http://trac.sagemath.org/sage_trac/ticket/6494 is a step in that >> direction.
+1. There's code up there just waiting for review. > Well, that is a different issue. I think that sage/tests/startup.py is > a bad test because it is too unpredictable. Sometimes it works, > sometimes it doesn't, depending for example on the load of the system. Well, that's an indication that things have gotten worse--it wasn't a problem for a long time despite the variance in system load. It's only tested on sage.math, and *should* start in under 1 second on a warmed up cache, and failures should be rare (baring an extremely loaded sage.math, which means the tester or someone else should be throttling back their use). Removing the test rather than fixing the problem is saying that excessive startup time isn't a bug. - Robert -- 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
