On Sat, Sep 18, 2010 at 6:17 AM, Niles <nil...@gmail.com> wrote: > >> > 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. > > indeed; I've had trouble with this too > >> Removing the test rather than fixing the problem is >> saying that excessive startup time isn't a bug. > > 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... > 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. - 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
