Only permit rank0 to mkdir when -d flag specified #955
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.
PR Summary
Evidently, @bprather and I are among the few who actually use the
-d
flag. This flag enables users to send all output data to a specified directory, e.g.,I have found on several occasions that when firing up a multi-rank job, I get a crash with an accompanying error message indicating that there was an error in creating the directory.
I think this issue is related to a race condition wherein multiple ranks were trying to create the same directory. The changes in this MR permit only rank 0 to create the directory. Then we call an
MPI_Barrier
in the unlikely chance that one rank tries tochdir
into a directory not yet created.PR Checklist