-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Enable manual test config label selection on Windows #84669
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/84669
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 335de21: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
How did you test this? Unless I'm misreading the data, looking at HUD it doesn't look like much was filtered out.
The CI run itself is the test. There are only functorch-related build and tests for Windows (and Linux) in HUD. You can also verify it using GitHub summary view https://github.com/pytorch/pytorch/actions/runs/3012171625 to see which tests are skipped and which are run. The latter is a bit easier IMO. Windows build and test would still happen because it has functorch there. Only those Windows default test-config shards are filtered out, so may be that's the reason you still see almost the same steps on HUD |
|
@pytorchbot merge -g |
|
@pytorchbot successfully started a merge job. Check the current status here. |
|
Hey @huydhn. |
Summary: After #83690, functorch team has started using the new label in some of their [PRs](https://github.com/pytorch/pytorch/labels/test-config%2Ffunctorch). So this enabled the same feature on Windows. ### Issues #82367 Pull Request resolved: #84669 Approved by: https://github.com/ZainRizvi Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/fe353e1413e2262993fb71dba7317f21bc6fc3bc Reviewed By: izaitsevfb Differential Revision: D39386410 Pulled By: izaitsevfb fbshipit-source-id: d1eb0a751c140d7048998d6b7c59cae132cc9c7d
Following up with #83690 and #84669, functorch team has started using the new label in some of their [PRs](https://github.com/pytorch/pytorch/labels/test-config%2Ffunctorch). This is to enable manual test config using label on GHA macos. This also works with `ciflow/mps` as follows: * If only `test-config/functorch` is present, no arm64 build is performed and mps test is skipped * If only `ciflow/mps` is present, mps test is run in addition to all other tests * If both `test-config/functorch` and `ciflow/mps` is present, both functorch and mps tests are run * If none of the label is present, pull workflow is run as usual ### Issues #82367 Pull Request resolved: #84895 Approved by: https://github.com/ZainRizvi
Following up with #83690 and #84669, functorch team has started using the new label in some of their [PRs](https://github.com/pytorch/pytorch/labels/test-config%2Ffunctorch). This is to enable manual test config using label on GHA macos. This also works with `ciflow/mps` as follows: * If only `test-config/functorch` is present, no arm64 build is performed and mps test is skipped * If only `ciflow/mps` is present, mps test is run in addition to all other tests * If both `test-config/functorch` and `ciflow/mps` is present, both functorch and mps tests are run * If none of the label is present, pull workflow is run as usual ### Issues #82367 Pull Request resolved: #84895 Approved by: https://github.com/ZainRizvi
After #83690, functorch team has started using the new label in some of their PRs. So this enabled the same feature on Windows.
Issues
#82367