Skip to content

Revert #169867#176485

Closed
angelayi wants to merge 1 commit intomainfrom
angelayi/revert_device_mesh
Closed

Revert #169867#176485
angelayi wants to merge 1 commit intomainfrom
angelayi/revert_device_mesh

Conversation

@angelayi
Copy link
Copy Markdown
Contributor

@angelayi angelayi commented Mar 4, 2026 •
edited
Loading

@angelayi angelayi requested a review from huydhn March 4, 2026 21:01
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Mar 4, 2026 •
edited
Loading

🔗 Helpful Links

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

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

❌ 1 New Failure, 14 Pending, 1 Unrelated Failure

As of commit bff8e6f with merge base e77361a (image):

NEW FAILURE - The following job has failed:

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

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

@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Mar 4, 2026

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

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

@angelayi angelayi force-pushed the angelayi/revert_device_mesh branch from ee9f0b9 to bff8e6f Compare March 4, 2026 21:04
@huydhn
Copy link
Copy Markdown
Contributor

huydhn commented Mar 4, 2026

@pytorchbot merge

@pytorch-bot pytorch-bot Bot added the ciflow/trunk Trigger trunk jobs on your pull request label Mar 4, 2026
@pytorchmergebot
Copy link
Copy Markdown
Collaborator

pytorchmergebot commented Mar 4, 2026

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

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

Details for Dev Infra team Raised by workflow job

@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Mar 4, 2026

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

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

@angelayi angelayi added the topic: not user facing topic category label Mar 4, 2026
@huydhn
Copy link
Copy Markdown
Contributor

huydhn commented Mar 5, 2026

@pytorchbot merge -f 'Signals look good'

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

pytorchmergebot commented Mar 5, 2026

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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

Vighaneshs pushed a commit to Vighaneshs/pytorch that referenced this pull request Mar 5, 2026
@angelayi @Vighaneshs
Revert pytorch#169867 (pytorch#176485)
d068a2c 
Reverts DeviceMesh tracing changes in pytorch#169867

Pull Request resolved: pytorch#176485
Approved by: https://github.com/huydhn
angelayi added a commit that referenced this pull request Mar 5, 2026
@angelayi
Revert #176485
0f84985 
This reverts commit 23c859c.
angelayi added a commit that referenced this pull request Mar 10, 2026
@angelayi
Revert #176485
1965e2c 
This reverts commit 23c859c.
EmanueleCoradin pushed a commit to EmanueleCoradin/pytorch that referenced this pull request Mar 30, 2026
@angelayi @EmanueleCoradin
Revert pytorch#169867 (pytorch#176485)
c8b3842 
Reverts DeviceMesh tracing changes in pytorch#169867

Pull Request resolved: pytorch#176485
Approved by: https://github.com/huydhn
@github-actions github-actions Bot deleted the angelayi/revert_device_mesh branch April 4, 2026 02:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@huydhn huydhn huydhn approved these changes

Assignees

No one assigned

Labels

ci-no-td Do not run TD on this PR ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request Merged module: dynamo topic: not user facing topic category

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@angelayi @huydhn @pytorchmergebot