-
Notifications
You must be signed in to change notification settings - Fork 636
migrate exir test to use torch.cond instead of the hop directly #12695
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/12695
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 1 New FailureAs of commit e45dacb with merge base e31eb56 ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D78696006 |
@pytorchbot label "release notes: none" |
…rch#12695) Summary: torch.cond is the use-facing api, which allows closure, have safety checks etc. Differential Revision: D78696006
…rch#12695) Summary: Pull Request resolved: pytorch#12695 torch.cond is the use-facing api, which allows closure, have safety checks etc. Differential Revision: D78696006
This pull request was exported from Phabricator. Differential Revision: D78696006 |
do torch.map and torch.while exist as well |
haven't yet, they can be accessed via torch._higher_order_ops.map/while_loop now |
Differential Revision: D78696006 Pull Request resolved: pytorch#12695
Summary: torch.cond is the use-facing api, which allows closure, have safety checks etc.
Differential Revision: D78696006