Skip to content

Revert getAllOperatorsFor changes (#167860, #162218)#169281

Closed
ezyang wants to merge 2 commits intogh/ezyang/3208/basefrom
gh/ezyang/3208/head
Closed

Revert getAllOperatorsFor changes (#167860, #162218)#169281
ezyang wants to merge 2 commits intogh/ezyang/3208/basefrom
gh/ezyang/3208/head

Conversation

@ezyang
Copy link
Contributor

@ezyang ezyang commented Dec 1, 2025 •
edited by pytorchmergebot
Loading

Stack from ghstack (oldest at bottom):

This reverts commit 567dcdb.
This reverts commit 0e7ccc0.

These changes break downstream builds and also are the suspected culprit of a memory corruption.

@ezyang
Update
23d02ad 
[ghstack-poisoned]
ezyang added a commit that referenced this pull request Dec 1, 2025
@ezyang
Revert getAllOperatorsFor changes (#167860, #162218)
3dd3f3b 
This reverts commit 567dcdb.
This reverts commit 0e7ccc0.


ghstack-source-id: fec7bf5
Pull-Request: #169281
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 1, 2025 •
edited
Loading

🔗 Helpful Links

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

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

❌ 1 New Failure, 4 Unrelated Failures

As of commit 6b66779 with merge base ded9bcd (image):

NEW FAILURE - The following job has failed:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

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

@pytorch-bot pytorch-bot bot added ci-no-td Do not run TD on this PR release notes: jit release notes category labels Dec 1, 2025
@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Dec 1, 2025
@pytorch-bot pytorch-bot bot removed the oncall: jit Add this issue/PR to JIT oncall triage queue label Dec 1, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 1, 2025

The label oncall: jit is only applicable to issues and has been removed. Please only use this label on issues.

@ezyang ezyang requested a review from zou3519 December 1, 2025 05:00
@ezyang ezyang added the ciflow/trunk Trigger trunk jobs on your pull request label Dec 1, 2025
@ezyang
Copy link
Contributor Author

ezyang commented Dec 1, 2025

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Dec 1, 2025

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

pytorchmergebot commented Dec 1, 2025

Merge failed

Reason: 7 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@ezyang
Copy link
Contributor Author

ezyang commented Dec 1, 2025

@pytorchbot merge -r

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Dec 1, 2025

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@ezyang
Update
6b66779 
[ghstack-poisoned]
@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Dec 1, 2025

Successfully rebased gh/ezyang/3208/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/169281)

pytorchmergebot pushed a commit that referenced this pull request Dec 1, 2025
@ezyang
Revert getAllOperatorsFor changes (#167860, #162218)
b725b8c 
This reverts commit 567dcdb.
This reverts commit 0e7ccc0.


ghstack-source-id: 950b6d8
Pull-Request: #169281
@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Dec 1, 2025

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

pytorchmergebot commented Dec 2, 2025

Merge failed

Reason: 1 jobs have failed, first few of them are: trunk / linux-jammy-rocm-py3.10 / test (default, 4, 6, linux.rocm.gpu.gfx942.1)

Details for Dev Infra team Raised by workflow job

ezyang added a commit to ezyang/pytorch that referenced this pull request Dec 4, 2025
@ezyang @facebook-github-bot
Revert getAllOperatorsFor changes (pytorch#167860, pytorch#162218) py…
20792f8 
…torch#169281

Summary:
This reverts commit 567dcdb.
This reverts commit 0e7ccc0.

These changes break downstream builds and also are the suspected culprit of a
memory corruption.

Test Plan: sandcastle

Differential Revision: D88394221
@ezyang
Copy link
Contributor Author

ezyang commented Dec 5, 2025

@pytorchbot merge -f "unrelated ci failures"

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Dec 5, 2025

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

umechand-amd pushed a commit to ROCm/pytorch that referenced this pull request Dec 8, 2025
@ezyang
Revert getAllOperatorsFor changes (pytorch#167860, pytorch#162218) (p…
6c3e00c 
…ytorch#169281)

This reverts commit 567dcdb.
This reverts commit 0e7ccc0.

These changes break downstream builds and also are the suspected culprit of a memory corruption.
Pull Request resolved: pytorch#169281
Approved by: https://github.com/zou3519, https://github.com/albanD
JacobSzwejbka pushed a commit that referenced this pull request Dec 8, 2025
@ezyang @JacobSzwejbka
Revert getAllOperatorsFor changes (#167860, #162218) (#169281)
3ae02a1 
This reverts commit 567dcdb.
This reverts commit 0e7ccc0.

These changes break downstream builds and also are the suspected culprit of a memory corruption.
Pull Request resolved: #169281
Approved by: https://github.com/zou3519, https://github.com/albanD
@github-actions github-actions bot deleted the gh/ezyang/3208/head branch January 4, 2026 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zou3519 zou3519 zou3519 approved these changes

@albanD albanD albanD approved these changes

@mikaylagawarecki mikaylagawarecki Awaiting requested review from mikaylagawarecki

@antoniojkim antoniojkim Awaiting requested review from antoniojkim

@bdhirsh bdhirsh Awaiting requested review from bdhirsh

@miladm miladm Awaiting requested review from miladm

@SherlockNoMad SherlockNoMad Awaiting requested review from SherlockNoMad

Assignees

No one assigned

Labels

ci-no-td Do not run TD on this PR ciflow/trunk Trigger trunk jobs on your pull request Merged release notes: jit release notes category

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@ezyang @pytorchmergebot @zou3519 @albanD @facebook-github-bot