cuda: Add a cuda component preset test#616
Open
Treece-Burgess wants to merge 2 commits into
Open
Conversation
Treece-Burgess
added
component-cuda
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pull Request Description
This PR adds a cuda component test titled
test_cuda_presetss.cuthat verifies the functionality of the GA100 and GH200 presets.This PR closes Issue #411.
Testing
Testing was done on Methane at ICL (1 * A100) with Cuda Toolkit 12.9 and Athena at Oregon (4 * A100) with Cuda Toolkit 12.8.1. In both cases,
test_cuda_presets.cupasses.Note: As stands, I am unable to test the functionality with a GH200 as the Hopper1 system at Oregon is not running properly. I am reaching out to the sysadmin there.
Author Checklist
Why this PR exists. Reference all relevant information, including background, issues, test failures, etc
Commits are self contained and only do one thing
Commits have a header of the form:
module: short descriptionCommits have a body (whenever relevant) containing a detailed description of the addressed problem and its solution
The PR needs to pass all the tests