Gihub CI: demonstrate fails when using OpenMPI 5.0.5 #1070
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wkliao
added
DO NOT MERGE
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After several tests using different versions of OpenMPI, it appears that
5.0.6 fixed the data sieving problem we suspect. This PR demonstrates
it by building Darshan with both 5.0.5 and 5.0.6. Only 5.0.5 failed.
The small test MPI program
mpi_file_write.ccalls onlyMPI_File_write()once, running on 4 MPI processes. when using OpenMPI 5.0.5, the test
program ran fine, but the contents of generated Darshan log file were corrupted.
According to OpenMPI 5.0.6 Release note:
UFS component to ensure data consistency, especially when using
data-sieving operations, which require broader locking.
Most likely relevant fix in OpenMPI 5.0.6 is open-mpi/ompi#12759