We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I created a test case in ompi-tests underibm/communicator/comm_idup_many.c
ibm/communicator/comm_idup_many.c
This test is doing a simple:
for (i = 0; i < num_comms_to_create; i++) { MPI_Comm_idup(MPI_COMM_WORLD, &comms[i], &req[i]); } MPI_Waitall(num_comms_to_create, req, MPI_STATUSES_IGNORE);
If you compile the v2.0.x branch with --enable-mpi-thread-multiple this test will hang when you try to create more than one communicator this way.
v2.0.x
--enable-mpi-thread-multiple
./configure --enable-debug --enable-mpi-thread-multiple
The problem is that the first request will progress past stage one, but the second request will block the progress thread in this section of code:
The master and v2.x branches pass this test. So I believe that the CID allocation fix that went into those two branches 'fixed' this problem.
master
v2.x
The text was updated successfully, but these errors were encountered:
As part of Issue #2234 it was requested that we port a portion of this change to the v2.0.x series to fix a spawn issue:
I believe that this commit to the v2.x branch is what we would be looking at:
Sorry, something went wrong.
Per the call today, #2381 may fix this issue.
Confirmed by @jjhursey: fixed by #2381.
hjelmn
jjhursey
No branches or pull requests
I created a test case in ompi-tests under
ibm/communicator/comm_idup_many.c
This test is doing a simple:
If you compile the
v2.0.x
branch with--enable-mpi-thread-multiple
this test will hang when you try to create more than one communicator this way.The problem is that the first request will progress past stage one, but the second request will block the progress thread in this section of code:
The
master
andv2.x
branches pass this test. So I believe that the CID allocation fix that went into those two branches 'fixed' this problem.The text was updated successfully, but these errors were encountered: