I see. Then you understand correctly - we are not going to fix the v1.10 series.
> On Nov 8, 2017, at 10:47 AM, Nikolas Antolin wrote:
>
> That was not my interpretation. His message said he did not observe the race
> condition for 2 processes, but did for 6 processes. I observe a failure to
>
That was not my interpretation. His message said he did not observe the
race condition for 2 processes, but did for 6 processes. I observe a
failure to exit mpirun around 25-30% of the time with 2 processes, causing
an inconsistent hang in both my example program and my larger application.
-Nik
O
According to the other reporter, it has been fixed in 1.10.7. I haven’t
verified that, but I’d suggest trying it first.
> On Nov 8, 2017, at 8:26 AM, Nikolas Antolin wrote:
>
> Thank you for the replies. Do I understand correctly that since OpenMPI v1.10
> is no longer supported, I am unlikel
Thank you for the replies. Do I understand correctly that since OpenMPI
v1.10 is no longer supported, I am unlikely to see a bug fix for this
without moving to v2.x or v3.x? I am dealing with clusters where the
administrators may be loathe to update packages until it is absolutely
necessary, and wa
Hi,
On Tue, Nov 07, 2017 at 02:05:20PM -0700, Nikolas Antolin wrote:
> Hello,
>
> In debugging a test of an application, I recently came across odd behavior
> for simultaneous MPI_Abort calls. Namely, while the MPI_Abort was
> acknowledged by the process output, the mpirun process failed to exit.
Hello,
In debugging a test of an application, I recently came across odd behavior
for simultaneous MPI_Abort calls. Namely, while the MPI_Abort was
acknowledged by the process output, the mpirun process failed to exit. I
was able to duplicate this behavior on multiple machines with OpenMPI
version
