[hipsparse] Part 8: Adding yaml test files to hipSPARSE #2360
+2,518
−4,625
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.
Motivation
The goal is to add yaml files for testing in hipSPARSE similar to how we
handle testing in rocSPARSE. This makes the testing cleaner and more
flexible. Doing this all in one PR however would result in a very large
number of file changes and file additions. In order to keep the PR size
more manageable, I am refactoring the hipSPARSE client code to support
yaml file testing in parts:
Part 1: Remove std::string from Arguments struct and only use
fixed sized char arrays COMPLETE
Part 2: Add code required to process yaml file testing, generate
binary data test file, and handle the dispatching of tests. COMPLETE
Part 3: Move level1 routines over to using yaml files. COMPLETE
Part 4: Move level2 routines over to using yaml files COMPLETE
Part 5: Move level3 routines over to using yaml files
Part 6: Move extra routines over to using yaml files
Part 7: Move precond routines over to using yaml files
Part 8: Move generic routines over to using yaml files
Part 9: Move conversion routines over to using yaml files
Technical Details
This first PR handles Part 8, namely moving generic routines to new yaml testing
Test Plan
All CI tests should pass