I ended up looking at this and it was a bug in this set of tests. Needed to check for MPI_COMM_NULL in a few places. This has been fixed.
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Rolf vandeVaart Sent: Thursday, April 02, 2015 10:10 AM To: de...@open-mpi.org Subject: [OMPI devel] Problems with some IBM neighbor tests I just recently bumped running some tests from np=4 to np=6. I am now seeing failures on the following tests in the ibm/collective directory. ineighbor_allgather, ineighbor_allgatherv, ineighbor_alltoall, ineighbor_alltoallv, ineighbor_alltoallw neighbor_allfather, neighbor_allgatherv, neighbor_alltoall, neighbor_alltoallv, neighbor_alltoallw The test fails like this: [rvandevaart@drossetti-ivy4 collective]$ mpirun -np 6 ineighbor_allgather Testing MPI_Neighbor_allgather on cartesian communicator [drossetti-ivy4:26205] *** An error occurred in MPI_Cart_coords [drossetti-ivy4:26205] *** reported by process [3563978753,4] [drossetti-ivy4:26205] *** on communicator MPI_COMM_WORLD [drossetti-ivy4:26205] *** MPI_ERR_COMM: invalid communicator [drossetti-ivy4:26205] *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, [drossetti-ivy4:26205] *** and potentially your MPI job) Pass! However, these tests appear to pass for multiples of 4 like np=4, 8, 12, 16, 20, etc... Anyone know if this bug in test or in library? This happens on both 1.8 and master. Thanks, Rolf ________________________________ This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ________________________________
