-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[LTC] Remove noop_execution_mode_ #89989
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
Summary: noop_execution_mode_ doesn't seem to be useful anymore. Let's remove it. Test Plan: CI.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/89989
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 07c29f1: 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.
LGTM
|
Thanks, Bin. |
|
@pytorchbot merge -g |
Merge startedYour change will be merged once all checks on your PR pass since you used the green (-g) flag (ETA: 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 additional jobs have failed, first few of them are: trunk Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot merge -f "tests are timed out but shouldn't be related." |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Summary: noop_execution_mode_ doesn't seem to be useful anymore. Let's remove it. Test Plan: CI. Pull Request resolved: pytorch#89989 Approved by: https://github.com/desertfire, https://github.com/JackCaoG
Summary:
noop_execution_mode_ doesn't seem to be useful anymore. Let's remove it.
Test Plan:
CI.