-
Notifications
You must be signed in to change notification settings - Fork 646
[Backend Tester] Add portable test flow #13250
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: gh/GregoryComer/112/head
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13250
Note: Links to docs will display an error until the docs builds have been completed. 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.
This is good.
@manuelcandales is planning to add a way to run through torch.nn.Module for Portable library testing (w/ Facto). This PR wants me to up the discussion we had @GregoryComer about using Facto here. And more generally make it possible to leverage Facto for backend hardening, which may require some changes in Facto, as @manuelcandales and I also discussed.
Can we align on this? And also on the long term direction?
Stamping this PR so you are not blocked Gregory but let's sync.
Add a portable tester flow to the backend tester. This is mainly intended to help validate the test suite and to get baseline numbers to compare against delegated results.