Hasn't this been discussed several times already? I consider startup time to be one of our biggest bugs... If we need to, lets bump it to 4 or even 10 seconds or something so at least we don't have egregious regressions. Or replace it with something better (e.g. it only fails if the load is so small, or looks at user time, or time(startup) < time(0.0x * sage -testall)).
On Mon, Jan 7, 2013 at 2:45 PM, Volker Braun <vbraun.n...@gmail.com> wrote: > I'm fine with removing the timing, but we should test somewhere that lazy > imports are not accidentally imported during startup. Right now that file > checks that numpy isn't imported. Though maybe it would be good to move it > to a better-named file ;-) > > > On Monday, January 7, 2013 10:21:53 PM UTC, Jeroen Demeyer wrote: >> >> The test in devel/sage/sage/tests/startup.**py has been bothering me for >> a >> while already. It's way too unreliable to be useful, it depends too >> much on the system load (both I/O and CPU). And system load on >> sage.math is quite high lately... Because of this, I tend to ignore >> this test anyway, so we might as well remove it. >> >> I'm all for replacing the test by something more objective which doesn't >> depend on the phase of the moon, but let's first get rid of the current >> stupid test. >> > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To post to this group, send email to sage-devel@googlegroups.com. > To unsubscribe from this group, send email to > sage-devel+unsubscr...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
