You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the suggestion
CI/CD that spans ALL modes in Omniperf. Obtaining access to test nodes with Instinct cards that can be used in this pipeline.
Justification
At the moment CI/CD is incomplete in Omniperf - it only covers a handful of analyze mode command combinations. Without access to hardware to test Omniperf's profiling capabilities, profile mode is completely overlooked. If we obtain access to a test node, our code coverage would increase tremendously.
Additionally, there may be some room to re-think the procedure for the test cases we add/cover. At the moment, I don't think there's much of a methodology to the random list of command combinations tested.
(i.e. Adding testing for --gui flag, checking values of output tables between runs, etc.)
Implementation
Steal an HPC Fund node from Karl
Access what hardware we can spare for this "testing node"
Some level of IT required to establish connection between workflow files and HPC Fund
Come to an agreement on how list of test cases will be generated
Additional Notes
May want to loop @JoseSantosAMD into this as he's the engineer who set existing CI/CD up
Describe the suggestion
CI/CD that spans ALL modes in Omniperf. Obtaining access to test nodes with Instinct cards that can be used in this pipeline.
Justification
At the moment CI/CD is incomplete in Omniperf - it only covers a handful of
analyze
mode command combinations. Without access to hardware to test Omniperf's profiling capabilities,profile
mode is completely overlooked. If we obtain access to a test node, our code coverage would increase tremendously.Additionally, there may be some room to re-think the procedure for the test cases we add/cover. At the moment, I don't think there's much of a methodology to the random list of command combinations tested.
(i.e. Adding testing for
--gui
flag, checking values of output tables between runs, etc.)Implementation
Additional Notes
May want to loop @JoseSantosAMD into this as he's the engineer who set existing CI/CD up
Originally posted by @coleramos425 in #153 (comment)
The text was updated successfully, but these errors were encountered: