-
Notifications
You must be signed in to change notification settings - Fork 646
[Backend Tester] Add LSTM tests #13238
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/pytorch/executorch/13238
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit 32881da with merge base 9c73b5d ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@@ -0,0 +1,208 @@ | |||
# Copyright (c) Meta Platforms, Inc. and affiliates. |
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.
Not sure if its an operator :P
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.
Yeah, this is true. The operator tests could also be considered nn.Module + torch API surface tests. Open to ideas. Some backends, like Core ML (I believe), consume LSTM as a whole module, so I wanted to test it atomically.
Add tests for the LSTM module. This is done in the context of #12898.