Add CTest testing framework.#135
Merged
Merged
Conversation
Signed-off-by: romerojosh <[email protected]>
Collaborator
Author
|
/build |
|
🚀 Build workflow triggered! View run |
|
✅ Build workflow passed! View run |
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.
This PR adds a more a extensive and direct CTest-based test suite to cuDecomp. The (now "legacy") test executables were useful for end-to-end coverage of the transpose and halo operations of the library, but coverage was primarily achieved via parameter sweeps. While these legacy tests were optimized to run these sweeps relatively quickly, they were still not well suited for per PR testing and required multi-GPU/multi-node hardware to cover all paths.
This new testing framework adopts a more conventional setup, with focused tests aimed at API coverage/contract validation and curated transpose/halo operation testing to achieve high coverage of all relevant paths. As for usability, the new tests have been designed to be able to run on a single GPU (via MPS), though 4 GPUs are the preferred set up. Refer to the updated test README.md for more details on the new tests and usage.
As these tests still require GPUs, they will not be integrated into the GitHub CI at this time.