Jeff, Less typing to launch 50+ testers than pick out just those two. Starting them now...
-Paul On Fri, Dec 19, 2014 at 12:22 PM, Jeff Squyres (jsquyres) < jsquy...@cisco.com> wrote: > > Paul -- > > The fix for this is now on the v1.8 branch. I'm spinning up a new nightly > tarball for you. > > http://www.open-mpi.org/nightly/v1.8/ > > Could you test it in the 2 cases where you had fortran failures? > > > > On Dec 18, 2014, at 8:50 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > > > Update: > > > > I now have 59 of 61 results, with only the QEMU-emulated MIPS platforms > outstanding. > > Those will not likely finish until near to (or after) midnight tonight. > > Unless something turns up on the MIPS systems my "smoke test" of rc5 is > complete. > > > > The only issues I found are the vader and fortran ones mentioned > previously. > > > > Nathan now has an account on the same SGI UV as I have been using. > > Jeff now has my configure and ompi_info output for my fortran failures. > > > > NOTE (primarily directed at Jeff): > > I define "issue" to *exclude* known problem with certain compilers that > are also present in earlier releases. In particular, I pass explicit > --with-mpi-fortran=XXX and/or --disable-oshmem-fortran options to configure > when using certain PGI and XLC versions because (as of 1.8.3 when I last > adjusted those settings) configure was not able to automatically disqualify > their "deficient" fortran support. If there is a desire/need to follow up > on this, let me know. However, all those "deficient" fortan compilers have > been reported by me on this list at least once in testing prior releases > (just never in one place). > > > > -Paul > > > > On Thu, Dec 18, 2014 at 8:55 AM, Paul Hargrove <phhargr...@lbl.gov> > wrote: > > With results from about 50 out of 61 platforms: > > > > + KNOWN: SGI UV is still "broken-by-default" (fails compiling vader > unless configured with --without-xpmem) > > + NEW: I see Fortran bindings failing to compile w/ gfortran > > + NEW: I see Fortran bindings fail to link with Open64 > > > > I also have unexplained errors on my Solaris-10/SPARC system. > > It looks like there may have been a loss of network connectivity during > the tests. > > I need to check these deeper, but I expect them to pass when I get a > chance to re-run them. > > > > -Paul > > > > -- > > Paul H. Hargrove phhargr...@lbl.gov > > Computer Languages & Systems Software (CLaSS) Group > > Computer Science Department Tel: +1-510-495-2352 > > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 > > > > > > -- > > Paul H. Hargrove phhargr...@lbl.gov > > Computer Languages & Systems Software (CLaSS) Group > > Computer Science Department Tel: +1-510-495-2352 > > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org > > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/12/16683.php > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/12/16697.php > -- Paul H. Hargrove phhargr...@lbl.gov Computer Languages & Systems Software (CLaSS) Group Computer Science Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
