[dynamo] fix error_on_graph_break bug where non-empty checkpoint results in unwanted graph break resumption#166586
[dynamo] fix error_on_graph_break bug where non-empty checkpoint results in unwanted graph break resumption#166586williamwen42 wants to merge 2 commits into
Conversation
…lts in unwanted graph break resumption [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/166586
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit faa392b with merge base df71b70 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Lucaskabela
left a comment
There was a problem hiding this comment.
Minor though on improving this debuggability
| or self.error_on_graph_break | ||
| or self.is_tracing_resume_prologue | ||
| ): | ||
| raise |
There was a problem hiding this comment.
Should we raise e here for error visibility?
There was a problem hiding this comment.
I think re-raise is standard Python practice? It's done below.
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
|
@pytorchbot merge |
|
The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
@pytorchbot cherry-pick --onto release/2.9 --fixes "error in new nested graphbreak feature (#166589)" -c fixnewfeature |
Cherry picking #166586Command Details for Dev Infra teamRaised by workflow job |
…lts in unwanted graph break resumption (pytorch#166586) Fixes pytorch#166589 Pull Request resolved: pytorch#166586 Approved by: https://github.com/Lucaskabela ghstack dependencies: pytorch#166476, pytorch#166477
…torch#166587) Pull Request resolved: pytorch#166587 Approved by: https://github.com/Lucaskabela ghstack dependencies: pytorch#166476, pytorch#166477, pytorch#166586
…lts in unwanted graph break resumption (#166925) [dynamo] fix error_on_graph_break bug where non-empty checkpoint results in unwanted graph break resumption (#166586) Fixes #166589 Pull Request resolved: #166586 Approved by: https://github.com/Lucaskabela ghstack dependencies: #166476, #166477 (cherry picked from commit 267d019) Co-authored-by: William Wen <williamwen@meta.com>
…lts in unwanted graph break resumption ghstack-source-id: 407b722 Pull Request resolved: pytorch/pytorch#166586
Stack from ghstack (oldest at bottom):
Fixes #166589
cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @chauhang @amjames @Lucaskabela @mlazos