-
Couldn't load subscription status.
- Fork 308
test: add ch4:ofi --hasgpu performance testfile #7519
New issue
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
Conversation
e7857c0 to
3baa7ef
Compare
9ab0ecb to
ee5b6c7
Compare
4b138e6 to
eeaaaff
Compare
|
Might be worth integrating #7536 into this depending on need. |
|
Looks good. How about squash some commits? Each commit should be self-contained and do not do two things at once. But we don't have to keep multiple commits history showing how a single thing (e.g. adding the -gpu option to tests) was developed. That latter has little value for maintenance. |
a89674b to
03cd8c1
Compare
|
Agreed, squashed the PR to three commits. Feel free to squash and merge to reduce it further if needed. |
Introduces a testlist running latency and bandwidth tests for senddev and recvdev (host/device) combinations. The result of this testlist is fed into gnuplot by the test suite to generate performance graph artifacts.
Reintroduces the `gpu` testlist flag removed in PR pmodels#7506 as `hasgpu=?`. However, it is now implemented as a GPU library dependency requirement which skips tests if they are not detected by Automake. Also adds a corresponding `MPITEST_HASGPU` environment variable for manual testing.
03cd8c1 to
529ff88
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Pull Request Description
This PR adds a performance
testlisttotests/mpi/benchfor a future ch4:ofi gpu performance build job. To be merged in once the test is stabilized.Author Checklist
Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
Commits are self-contained and do not do two things at once.
Commit message is of the form:
module: short descriptionCommit message explains what's in the commit.
Whitespace checker. Warnings test. Additional tests via comments.
For non-Argonne authors, check contribution agreement.
If necessary, request an explicit comment from your companies PR approval manager.