-
Notifications
You must be signed in to change notification settings - Fork 607
Support to init BundledProgram from pte file #7278
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/7278
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 892a2ee with merge base 343aa0c ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D67013542 |
Summary: Added an optional `pte_file_path` arg to BundledProgram's init function. This is to allow users to create bundled program with varied inputs after exporting. Reviewed By: tarun292 Differential Revision: D67013542
d0d1d44
to
892a2ee
Compare
This pull request was exported from Phabricator. Differential Revision: D67013542 |
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 seem to cause major problem
from pyre_extensions import none_throws
As pyre is not installed in the github project. I kicked of a revert to test if and added the trunk flag to get more testing on it.
@zingo - Wonder why the CI here is clean. |
This revert is maybe not be the thing you want to do, I just used it to highlight the problems, and test if it solves it. |
Summary: Added an optional
pte_file_path
arg to BundledProgram's init function. This is to allow users to create bundled program with varied inputs after exporting.Differential Revision: D67013542