Skip to content

dynamo: Write a structured trace for supressed exceptions.#160151

Closed
c00w wants to merge 1 commit intogh/c00w/54/basefrom
gh/c00w/54/head
Closed

dynamo: Write a structured trace for supressed exceptions.#160151
c00w wants to merge 1 commit intogh/c00w/54/basefrom
gh/c00w/54/head

Conversation

@c00w
Copy link
Contributor

@c00w c00w commented Aug 8, 2025

Stack from ghstack (oldest at bottom):

Trying to understand a supressed exception when nothing shows up in TLParse is
relatively confusing. Logging this explicitly to make it elss confusing.

This also needs a TLParse diff to finish it.

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @chauhang @amjames @Lucaskabela

Trying to understand a supressed exception when nothing shows up in TLParse is
relatively confusing. Logging this explicitly to make it elss confusing.

This also needs a TLParse diff to finish it.

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Aug 8, 2025

🔗 Helpful Links

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

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

❌ 6 New Failures, 4 Unrelated Failures

As of commit ba5758b with merge base aeb5321 (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

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

c00w added a commit that referenced this pull request Aug 8, 2025
Trying to understand a supressed exception when nothing shows up in TLParse is
relatively confusing. Logging this explicitly to make it elss confusing.

This also needs a TLParse diff to finish it.

ghstack-source-id: 550ce8b
Pull Request resolved: #160151
@github-actions
Copy link
Contributor

github-actions bot commented Oct 7, 2025

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the Stale label Oct 7, 2025
@github-actions github-actions bot closed this Nov 6, 2025
@github-actions github-actions bot deleted the gh/c00w/54/head branch December 7, 2025 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant