KEMBAR78
[ONNX] Drop draft_export in exporter API by titaiwangms · Pull Request #161454 · pytorch/pytorch · GitHub
Skip to content

Conversation

@titaiwangms
Copy link
Collaborator

@titaiwangms titaiwangms commented Aug 26, 2025

If onnx exporter fallbacks to draft_export with big models, this is taking forever for users, and possibly spam the printout, which keeps users from their stack trace with strict=False.

We could consider make another API for draft_export as debugging tool, or combine it with report=True when "model is small"?

cc @justinchuby

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 26, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/161454

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 94ffaa7 with merge base ca9fe01 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added the release notes: onnx torch.onnx related changes that should show up in the release notes label Aug 26, 2025
@titaiwangms titaiwangms added module: onnx Related to torch.onnx topic: new features topic category labels Aug 26, 2025
@soulitzer soulitzer added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Aug 26, 2025
@titaiwangms
Copy link
Collaborator Author

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Aug 26, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your 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

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 2 jobs have failed, first few of them are: trunk / win-vs2022-cuda12.6-py3 / build, trunk / win-vs2022-cpu-py3 / build

Details for Dev Infra team Raised by workflow job

@titaiwangms
Copy link
Collaborator Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your 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

Advanced Debugging
Check the merge workflow status
here

@justinchuby justinchuby added topic: bc breaking topic category and removed topic: new features topic category labels Aug 26, 2025
pytorchmergebot pushed a commit that referenced this pull request Sep 5, 2025
Use `TORCH_ONNX_ENABLE_DRAFT_EXPORT` to control whether draft_export should be used as a strategy in onnx export.

Follow up of #161454

Pull Request resolved: #162225
Approved by: https://github.com/xadupre, https://github.com/titaiwangms
daisyden pushed a commit to daisyden/pytorch that referenced this pull request Sep 8, 2025
Use `TORCH_ONNX_ENABLE_DRAFT_EXPORT` to control whether draft_export should be used as a strategy in onnx export.

Follow up of pytorch#161454

Pull Request resolved: pytorch#162225
Approved by: https://github.com/xadupre, https://github.com/titaiwangms
markc-614 pushed a commit to markc-614/pytorch that referenced this pull request Sep 17, 2025
If onnx exporter fallbacks to draft_export with big models, this is taking forever for users, and possibly spam the printout, which keeps users from their stack trace with strict=False.

We could consider make another API for draft_export as debugging tool, or combine it with report=True when "model is small"?

Pull Request resolved: pytorch#161454
Approved by: https://github.com/justinchuby
markc-614 pushed a commit to markc-614/pytorch that referenced this pull request Sep 17, 2025
Use `TORCH_ONNX_ENABLE_DRAFT_EXPORT` to control whether draft_export should be used as a strategy in onnx export.

Follow up of pytorch#161454

Pull Request resolved: pytorch#162225
Approved by: https://github.com/xadupre, https://github.com/titaiwangms
mansiag05 pushed a commit to mansiag05/pytorch that referenced this pull request Sep 22, 2025
Use `TORCH_ONNX_ENABLE_DRAFT_EXPORT` to control whether draft_export should be used as a strategy in onnx export.

Follow up of pytorch#161454

Pull Request resolved: pytorch#162225
Approved by: https://github.com/xadupre, https://github.com/titaiwangms
cleonard530 pushed a commit to cleonard530/pytorch that referenced this pull request Sep 22, 2025
Use `TORCH_ONNX_ENABLE_DRAFT_EXPORT` to control whether draft_export should be used as a strategy in onnx export.

Follow up of pytorch#161454

Pull Request resolved: pytorch#162225
Approved by: https://github.com/xadupre, https://github.com/titaiwangms
dsashidh pushed a commit to dsashidh/pytorch that referenced this pull request Sep 26, 2025
Use `TORCH_ONNX_ENABLE_DRAFT_EXPORT` to control whether draft_export should be used as a strategy in onnx export.

Follow up of pytorch#161454

Pull Request resolved: pytorch#162225
Approved by: https://github.com/xadupre, https://github.com/titaiwangms
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged module: onnx Related to torch.onnx open source release notes: onnx torch.onnx related changes that should show up in the release notes topic: bc breaking topic category triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants