TST: aurora daos system profile #1027
Merged
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
shanedsnyder
force-pushed
the
snyder/aurora-daos-system-profile
branch
from
24486db to
17bd62f
Compare
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.
Add a new system profile for ALCF Aurora, targeting DAOS FUSE mounts, specifically.
Also, rename the old Aurora system profile to make it clear which is for DAOS and which is for Lustre.
Also, generalize a few of the regression test cases to look for both POSIX and DFS modules before checking counter values -- this allows the test to support MPI-IO over POSIX as well as MPI-IO over DFS.
Also, fix a small bug related to the scope of Darshan instrumentation within the
filenoroutine. We should only be calling Darshan core library functions if Darshan is enabled, so move thePRE_RECORD/POST_RECORDmacros to enforce that. This was causing crashes in Darshan's shutdown routine when writing logs to DAOS volumes in my testing, likely because Darshan was trying to instrument I/O it was issuing to open/write its own log file.