On Sat, Aug 21, 2010 at 6:17 PM, Mitesh Patel <qed...@gmail.com> wrote: > On 08/12/2010 05:01 PM, Mitesh Patel wrote: >> On 08/11/2010 07:19 PM, Robert Bradshaw wrote: >>> Thanks for looking into this, another data point is really helpful. I >>> put a vanilla Sage in hudson and for a while it was passing all of its >>> tests every time, then all of the sudden it started failing too. Very >>> strange... For now I've resorted to starting up Sage in a loop (as the >>> segfault always happened during startup) and am seeing about a 0.5% >>> failure rate (which is the same that I see with a vanilla Sage). >>> Hopefully we can get the parallel testing to work much more reliably >>> so we can use it as a good indicator in our Cython build farm to keep >>> people from breaking Sage (and I'm honestly really surprised we >>> haven't run into these issues during release management as well...) >> >> Strange, indeed. >> >> Could the startup segfault be distinct from and not present among the >> doctest faults? Testing about 2500 files with a 0.5% startup failure >> rate would give us about 13 extra, random(?) faults per run, which we >> don't see. > > Or should that be 0.05%?
Sorry, yes, 0.05%. > Some more data: I batch-tested 'sage -c "quit"' about 1.2e6 times with > vanilla 4.5.3.alpha1 on sage.math. Each run ended with exit status 0 > and no cores or discernible errors. Nice. Not sure what changed, but sounds like something did. - 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
