-
Notifications
You must be signed in to change notification settings - Fork 24.9k
[MPS] Add test/test_nn.py
to test suite
#134184
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/134184
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit c521e3c with merge base af66488 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot label "module: mps" "topic: not user facing" |
This will likely fail, but I'll try anyways so maybe I can get some feedback for macOS 13 and 15. @pytorchbot label "ciflow/mps" |
Can't add following labels to PR: ciflow/mps. Please ping one of the reviewers for help. |
Requesting approval for this change from @kulinseth or @malfet as code owners for MPS. |
46153a2
to
c2eff44
Compare
@hvaara thanks for opening this pr. I went ahead and launched your CI run so we can see what happens, but just fyi that I may open a separate pr to add test_nn and a few others to the mps flow |
Thanks @skotapati!
I don't understand. Do you mean you want me to split this up, or did you mean you're already working on something similar? Do you have a PR? Attempting to add MPS ciflow again. @pytorchbot label "ciflow/mps" |
Tests pass on macOS 14 and 15. Detected failure on macOS 13: @pytorchbot label keep-going |
I think that was the last of it in MPS - adding trunk. @pytorchbot label ciflow/trunk |
Can't add following labels to PR: ciflow/trunk. Please ping one of the reviewers for help. |
a46ae8c
to
b149887
Compare
b149887
to
c19005d
Compare
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.
SGTM
How do you plan to track these disables to work on fixing them?
Merge failedReason: 1 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
@hvaara you need to fix lint before this change can go in (and I can't do it for you, as you do not accept changes from contributors on your fork of PyTorch) |
Thanks for looking, @malfet. Fixed it and ran The following option is enabled ![]() am I missing something? |
How will they be picked up by |
@pytorchbot merge -f "Lint is green and CI was green during previous iteration" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
test_nn.py is running as part of trunk workflow, and it should cover MPS as well after your change, see https://github.com/pytorch/pytorch/actions/runs/10568390813/job/29279246604 |
Do you mean it's sufficient to set |
git show 1565940114aa271749e6395948ae81ff259868b4 | grep -e '^+.*issues/' | sed -e 's#.*issues/##' | sort -h | uniq xref:
|
Updating the comments with references to better places for context now that the bugs have been identified. xref #135442 #135447 #134184 Pull Request resolved: #135448 Approved by: https://github.com/ezyang
This PR increases test coverage by including the tests in `test/test_nn.py` in the test suite of MPS. Some of the tests are decorated with `@expectedFailureMPS` for various reasons. Either that the op is not implemented, or that the outputs do not align. Those tests that contain differing results should be investigated further to rule out any live bugs. ```bash $ python test/run_test.py --mps --verbose -k TestNN Running test batch 'tests to run' cost 84.76 seconds ``` Ref pytorch#133520 Pull Request resolved: pytorch#134184 Approved by: https://github.com/albanD, https://github.com/malfet
Updating the comments with references to better places for context now that the bugs have been identified. xref pytorch#135442 pytorch#135447 pytorch#134184 Pull Request resolved: pytorch#135448 Approved by: https://github.com/ezyang
Updating the comments with references to better places for context now that the bugs have been identified. xref pytorch#135442 pytorch#135447 pytorch#134184 Pull Request resolved: pytorch#135448 Approved by: https://github.com/ezyang
This PR increases test coverage by including the tests in
test/test_nn.py
in the test suite of MPS.Some of the tests are decorated with
@expectedFailureMPS
for various reasons. Either that the op is not implemented, or that the outputs do not align. Those tests that contain differing results should be investigated further to rule out any live bugs.Ref #133520
cc @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen