Skip to content

support back propagate debug handle to arbitrary ancestor export graph #12943

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 29, 2025
Merged

support back propagate debug handle to arbitrary ancestor export graph #12943

merged 1 commit into from
Jul 29, 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: #12580 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/26/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/gasoonjia/26/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/gasoonjia/26/orig
@diff-train-skip-merge

@Gasoonjia
support back propagate debug handle to arbitrary ancestor export graph
80c8ed8 
Pull Request resolved: #12580

Currently propagate_back_debug_handle function can only support propagating debug handle back to the greatest ancestor export graph.
This diff update algo to support every possible ancestor export graph on the flow.
ghstack-source-id: 299039097

Differential Revision: [D78464992](https://our.internmc.facebook.com/intern/diff/D78464992/)
@pytorchbot pytorchbot requested a review from Gasoonjia as a code owner July 29, 2025 02:28
@pytorch-bot PyTorch Bot
Copy link

pytorch-bot bot commented Jul 29, 2025 •
edited
Loading

🔗 Helpful Links

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

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

⏳ 32 Pending, 1 Unrelated Failure

As of commit 80c8ed8 with merge base 45846c8 (image):

BROKEN TRUNK - The following job 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 29, 2025
@github-actions GitHub Actions
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@Gasoonjia Gasoonjia merged commit c5dd931 into main Jul 29, 2025
98 of 100 checks passed
@Gasoonjia Gasoonjia deleted the gh/gasoonjia/26/orig branch July 29, 2025 03:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Gasoonjia Gasoonjia Gasoonjia approved these changes

Assignees
No one assigned
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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@pytorchbot @Gasoonjia @facebook-github-bot