mabshoff wrote: > > > On May 4, 7:57 am, Jaap Spies <j.sp...@hccnet.nl> wrote: >> mabshoff wrote: > > <SNIP> > >>> Well, I knew FLINT still ran its test suite and given we updated MPIR >>> I do prefer for it to run. There was also no 3.4.2 ticket to turn it >>> off :p. >> This testing feels ok for alpha and rc releases, but not on a final >> source release. IIRC this was standard procedure. > > Nope, it was commonly handled that way. But since the 'real' releases > are build more widely that either alpha or rc releases I have been > changing this to even run some test suites even then. This has already > flushed out various bugs in MPIR and in the past also FLINT. This > might seem like a waste of time to some people, but compared to > running Sage's test suite it seems like a low price to pay. >
Agreed, but how often did you get feedback from failures in the FLINT library from users of the 'real' releases in the field? > You wouldn't consider running the test suite a waste of time either I > assume. If someone really wants to we can introduce a special > SAGE_CHECK_OVEWRITE flag that completely turns off all checks if > anyone does thing this is really desirable, but I am hesitant to do > so. Testing makes software better and way too often has a point > upgrade that was supposedly safe introduced problems, so I am always > in favor of testing. > +1 for the last sentence. On relative slow hardware it looks like a good idea to make installation of ATLAS and e.g. FLINT less time consuming. Jaap --~--~---------~--~----~------------~-------~--~----~ 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 For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
