In fact, the only failure I see "out-of-the-box" in the test reports
http://wiki.sagemath.org/mpir/BuildFarm/mpir-2.1.0#MPIR2.1.0-rc2 are either with 1) gcc 4.3.2 which is a known broken compiler - we shouldn't be reporting test failures with arch/OS combinations due to broken compiler versions on the test machines. 2) core2 on fulvia which is most likely due to a problem with the setup of the machine itself, not in MPIR? If not, this should really have been fixed before release, but I think Jason's diagnosis was that it wasn't MPIR that was at fault. The other failures reported in the final column are only when the test script pushes MPIR into bizarre configurations which aren't what a user is going to choose. They aren't "out-of-the-box" configurations. Again, if not, they should really have been fixed before release, but again I thought the diagnosis was they weren't important. Bill. On 9 June 2010 01:05, Bill Hart <[email protected]> wrote: > Thanks very much Minh for all the hard work in doing the release > management for MPIR 2.1.0 !! > > By the way, we can remove this from the list of known problems on the > MPIR website: > > * MPIR normalises its extended GCD differently to GMP 5.0.1. - trac #293 > > I'm also confused by the reds in the testing matrix. Are these actual > MPIR failures or are they merely due to broken compilers, incorrectly > set up machines or invalid ABIs in the test script? > > I would simply list them as white "unavailable" if we have no passed > build reports for a given arch/OS combination. I don't think we should > be reporting failures with MPIR that have nothing to do with MPIR. Of > course if they are genuine failures, then we should have tickets for > them and notes in the "known problems" section of the website. > > Bill. > > On 9 June 2010 00:38, Minh Nguyen <[email protected]> wrote: >> Hi folks, >> >> MPIR 2.1.0 was released on 08th June 2010. >> >> * source tarball: http://www.mpir.org/mpir-2.1.0.tar.gz >> * documentation: http://www.mpir.org/mpir-2.1.0.pdf >> * full changelog: http://www.mpir.org/changes.html >> >> See the MPIR website (www.mpir.org) for known issues and a list of >> supported platforms/hardware in the form of the test matrix. >> >> The main features and changes in this release cycle are: >> >> * Fixed the xgcd normalisation issue and redid the tuning code for gcd and >> xgcd >> * Fixes for compiling with GCC 4.5.0 on Itanium >> * Initial build with Visual Studio 2010 >> * Export new function mpn_sqr >> >> Starting from MPIR 2.1.0, our procedure for managing an MPIR release >> is documented at >> >> http://www.mpir.org/release.html >> >> -- >> Regards >> The MPIR Team >> >> -- >> You received this message because you are subscribed to the Google Groups >> "mpir-devel" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/mpir-devel?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
