-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Introduce test skip markers for Sandcastle #150934
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
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/150934
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ You can merge normally! (1 Unrelated Failure)As of commit 7787ede with merge base 09e5a93 ( UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
4fb8c4d
to
86c8248
Compare
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
86c8248
to
224bffc
Compare
Rebased and conflicts resolved. Can this be reviewed please? |
Simplify the markers a bit to make them more expressive
224bffc
to
7787ede
Compare
Simplify the markers a bit to make them more expressive
It also makes it easier to skip those tests "manually" by changing the single definition of the skip marker.
This is important to reduce potential false positives (of failed tests) in some environments, such as HPC clusters
cc @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @pragupta @EikanWang @jgong5 @wenzhe-nrv @sanchitintel