Skip to content

propagate debug handle from edge dialect graph back to exported graph #12337

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

Merged
merged 2 commits into from
Jul 10, 2025

Conversation

pytorchbot
Copy link
Collaborator

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #12330 by @Gasoonjia
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/gasoonjia/19/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/gasoonjia/19/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/gh/gasoonjia/18/orig
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/gasoonjia/19/orig
@diff-train-skip-merge

Gasoonjia added 2 commits July 9, 2025 22:10
Pull Request resolved: #12288

Currently ExecuTorch debug handle infra traces operator transformation starting from export program. This diff makes etrecord support recording export program for further analysis use.

ghstack-source-id: 295312924
@exported-using-ghexport

Differential Revision: [D77965102](https://our.internmc.facebook.com/intern/diff/D77965102/)
Pull Request resolved: #12330

Using exported graph from torch.export as source of truth for aot intermediate output is our target. Once thing blocking us is the exported graph does not have debug handle, which will not show up in the export flow until DebugHandleGenerationPass, the last step of to_edge(). We need to equip the graph with same debug handle used in ExecuTorch flow.

This diff creates a propagate_back_debug_handle function, which propagate debug handle from edge dialect program back to the exported program while maintain the correctness of operator tracing.
ghstack-source-id: 295337600
@exported-using-ghexport

Differential Revision: [D78051614](https://our.internmc.facebook.com/intern/diff/D78051614/)
Copy link

pytorch-bot bot commented Jul 10, 2025

🔗 Helpful Links

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

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

❌ 4 New Failures, 3 Unrelated Failures

As of commit 1169788 with merge base dd06b3b (image):

NEW FAILURES - The following jobs have failed:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 10, 2025
Base automatically changed from gh/gasoonjia/18/orig to main July 10, 2025 23:06
Copy link
Contributor

@Gasoonjia Gasoonjia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it breaks oss cis because the core update the pr relies on haven't include into their nightly version yet. Should be auto-solved by the end of tmr

@Gasoonjia Gasoonjia merged commit 3419b46 into main Jul 10, 2025
89 of 96 checks passed
@Gasoonjia Gasoonjia deleted the gh/gasoonjia/19/orig branch July 10, 2025 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants