Re: [OMPI devel] [mpich-discuss] BUG in ADIOI_NFS_WriteStrided

On 12/19/2014 02:33 PM, Eric Chamberland wrote: Hi Howard, the bug is present also with MPICH-3.1.3... So, for disc...@mpich.org list readers, here is the valgrind output for a bug revealed with valgrind (sorry, I didn't compiled MPICH in debug mode), reported to OpenMPI earlier today: http:

Re: [OMPI devel] [1.8.4rc5] preliminary results

Thank you! On Dec 19, 2014, at 6:46 PM, Paul Hargrove wrote: > A quick glance at the results for the two "configurations of interest" appear > to show the problem is resolved. > > Tonight I will take a complete look through my results and report ONLY if I > find new regressions. > Unless you

Re: [OMPI devel] [1.8.4rc5] preliminary results

A quick glance at the results for the two "configurations of interest" appear to show the problem is resolved. Tonight I will take a complete look through my results and report ONLY if I find new regressions. Unless you hear from me, assume "openmpi-v1.8.3-322-g562a764" gets my "thumbs up" with re

Re: [OMPI devel] [1.8.4rc5] preliminary results

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. >

[OMPI devel] BUG in ADIOI_NFS_WriteStrided

Hi Howard, the bug is present also with MPICH-3.1.3... So, for disc...@mpich.org list readers, here is the valgrind output for a bug revealed with valgrind (sorry, I didn't compiled MPICH in debug mode), reported to OpenMPI earlier today: http://www.open-mpi.org/community/lists/devel/2014/12

Re: [OMPI devel] [1.8.4rc5] preliminary results

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 wrote: > Update: > > I now have 59 of 6

Re: [OMPI devel] BUG in ADIOI_NFS_WriteStrided

HI Eric, Does your app also work with MPICH? The romio in Open MPI is getting a bit old, so it would be useful to know if you see the same valgrind error using a recent MPICH. Howard 2014-12-19 9:50 GMT-07:00 Eric Chamberland : > > Hi, > > I encountered a new bug while testing our collective M

Re: [OMPI devel] FT code (again)

George is correct; opal_pmix.fence replaces the grpcomm barrier. Josh On Fri, Dec 19, 2014 at 10:47 AM, George Bosilca wrote: > > A opal_pmix.fence seems like a perfect replacement. > > George. > > > On Fri, Dec 19, 2014 at 10:26 AM, Adrian Reber wrote: > >> Again I am trying to get the FT co

Re: [OMPI devel] [1.8.4rc5] preliminary results

Wow! Thanks - I was turning blue… Actually, truly do appreciate all the tests you run for us! > On Dec 19, 2014, at 9:03 AM, Paul Hargrove wrote: > > > On Thu, Dec 18, 2014 at 5:50 PM, Paul Hargrove > wrote: > Unless something turns up on the MIPS systems my "smoke

Re: [OMPI devel] [1.8.4rc5] preliminary results

On Thu, Dec 18, 2014 at 5:50 PM, Paul Hargrove wrote: > > Unless something turns up on the MIPS systems my "smoke test" of rc5 is > complete. In case anybody was holding their breath: The MIPS testers completed just fine. -Paul -- Paul H. Hargrove phhargr...@lbl.gov

Re: [OMPI devel] [1.8.4rc5] preliminary results

Gilles, Whether we think this is a Open64 issue or not, this complier worked with 1.8.3 and 1.8.4rc4. I don't know the nature of the Fortran changes between rc4 and rc5, but perhaps they can be made conditional to allow Open64 to work with 1.8.4? I will sent configure output off-list momentarily

[OMPI devel] BUG in ADIOI_NFS_WriteStrided

Hi, I encountered a new bug while testing our collective MPI I/O functionnalities over NFS. This is not a big issue for us, but I think someone should have a look at it. While running at 3 processes, we have this error on rank #0 and rank #2, knowing that rank #1 have nothing to write (0 le

[OMPI devel] Git security vulnerability, please upgrade Windows & OS X Git clients

Quoting from https://github.com/blog/1938-vulnerability-announced-update-your-git-clients """ A critical Git security vulnerability has been announced today, affecting all versions of the official Git client and all related software that interacts with Git repositories, including GitHub for Win

Re: [OMPI devel] FT code (again)

A opal_pmix.fence seems like a perfect replacement. George. On Fri, Dec 19, 2014 at 10:26 AM, Adrian Reber wrote: > Again I am trying to get the FT code working. This time I am unsure how > to resolve the code changes from this commit: > > commit aec5cd08bd8c33677276612b899b48618d271efa > Au

[OMPI devel] FT code (again)

Again I am trying to get the FT code working. This time I am unsure how to resolve the code changes from this commit: commit aec5cd08bd8c33677276612b899b48618d271efa Author: Ralph Castain List-Post: devel@lists.open-mpi.org Date: Thu Aug 21 18:56:47 2014 + Per the PMIx RFC: This incl

Re: [OMPI devel] Still getting DDT test assert fails

I posted the full output from running the test on the still-open issue about this: https://github.com/open-mpi/ompi/issues/294#issuecomment-67638568 On Dec 19, 2014, at 6:46 AM, Jeff Squyres (jsquyres) wrote: > George -- > > You uncommented the "#if 0 ..." section in the opal datatype te

[OMPI devel] Still getting DDT test assert fails

George -- You uncommented the "#if 0 ..." section in the opal datatype test yesterday (https://github.com/open-mpi/ompi/commit/1895f29537820ee06492ae3b2e66c1cf5ef78c70), but we're still getting assert fails on opal_datatype_test. It caused the nightly tarball to fail last night, and I'm able t

Re: [OMPI devel] [1.8.4rc5] preliminary results

Paul, i faced the very same issue with open64-5.0 here is attached a simple reproducer. main2 can be built, but main cannot be built. the only difference is than unlike main.F90, main2.F90 contains a line : use, intrinsic :: iso_c_binding /* and they both link with libfoo.so, and foo.F90 *does*

Re: [OMPI devel] libfabric, config.h and hwloc

Jeff, the include path is $top_srcdir/opal/mca/event/libevent2021/libevent and the libevent config.h is in $top_builddir/opal/mca/event/libevent2021/libevent so if you do not use VPATH, $top_srcdir = $top_builddir and make success, but since i use VPATH, $top_srcdir != $top_builddir and there is