Re: [OMPI devel] Paul's testing summary

2014-01-17 Thread Jeff Squyres (jsquyres)
On Jan 17, 2014, at 1:30 AM, Paul Hargrove wrote: > [snipping CLOSED issues] > > 4. oob:tcp not using loopback interface for single-node runs > NOT YET, but not critical Ralph: is this deferred to v1.7.5? > 5. pgi-8 and pgi-9 fail building mpi_f08 > Looks like Jeff fixed the only real issue ea

Re: [OMPI devel] Paul's testing summary

2014-01-17 Thread Paul Hargrove
Current status of my seven issues as of tonight's trunk tarball (1.9a1r30302) 1. opal/util/path.c CLOSED 2. oshem_info reports oshmem:bindings:fort:yes unconditionally CLOSED (except for harmless orphaned call to OSHMEM_SETUP_CFLAGS) 3. configure refuses btl:verbs on Solaris CLOSED 4. oob:tcp n

Re: [OMPI devel] Paul's testing summary

2014-01-12 Thread Paul Hargrove
On Sun, Jan 12, 2014 at 9:35 AM, Ralph Castain wrote: > This should have been fixed by r30226 - was it not? > > > On Jan 11, 2014, at 3:29 PM, Paul Hargrove wrote: > > 2. oshem_info reports oshmem:bindings:fort:yes unconditionally > NO CHANGE (that I am aware of) > > Nope. System w/o a Fortran

Re: [OMPI devel] Paul's testing summary

2014-01-12 Thread Ralph Castain
This should have been fixed by r30226 - was it not? On Jan 11, 2014, at 3:29 PM, Paul Hargrove wrote: > 2. oshem_info reports oshmem:bindings:fort:yes unconditionally > NO CHANGE (that I am aware of) > >

Re: [OMPI devel] Paul's testing summary

2014-01-11 Thread Paul Hargrove
One addition: 7. netbsd6 static link failure (aio support resides in librt) FIX PROPOSED See thread beginning with http://www.open-mpi.org/community/lists/devel/2014/01/13591.php I have just now proposed a patch that resolves the problem for me. This issue impacts both trunk and v1.7. -Paul On

Re: [OMPI devel] Paul's testing summary

2014-01-11 Thread Paul Hargrove
Updates: 1. opal/util/path.c RESOLVED My testing on both trunk and v1.7 passed on all my platforms. Marco's reports success (after applying the usual patches) with the trunk on Cygwin. 2. oshem_info reports oshmem:bindings:fort:yes unconditionally NO CHANGE (that I am aware of) 3. configure refu