Repository navigation
test(miopen)[ALMIOPEN-2867]: add find/optimizer/misc gtest families to test_categories.yaml (1/9) #13403
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
Closed
aalabsi-amd
wants to merge
1
commit into
develop
from
users/aalabsi-amd/miopen-test-categories-jenkins-parity-01-find-optimizers-misc
Closed
test(miopen)[ALMIOPEN-2867]: add find/optimizer/misc gtest families to test_categories.yaml (1/9) #13403
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
This comment seems to imply that all the Full/* tests that were just added only run in comprehensive/full, but that is only true for a subset of these. Are these primarily Smoke/* tests? If so, we could add that explicitly here (or add one generic Smoke/* line, maybe immediately before Standard/*, below)
Maybe moving to Smoke/, Standard/, Full/* could help clean this up, so I am okay if you want to defer this
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.
One more note: you mention testing on standard, comprehensive and full in the TestPlan. Can we make this a checkbox list and also add doing sweeps on other architectures, such as gfx90a, navi, etc, or we might get surprised by nightly failures. The rock tests some architectures that our Jenkins CI didn't cover, and we have different timeout constraints for the rock's GHA vs Jenkins. Thanks!