Skip to content

[BE] Modify PyObjectSlot the assume only a single interpreter is in use #158407

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

Closed
wants to merge 9 commits into from

Conversation

PaliC
Copy link
Contributor

@PaliC PaliC commented Jul 16, 2025

Stack from ghstack (oldest at bottom):

This PR makes some less risky changes to PyObjectSlot as there is a lot of stuff we do not need since there is only one interpreter. Specifically check_interpreter and has_pyobj_nonhermetic are removed

Copy link

pytorch-bot bot commented Jul 16, 2025

🔗 Helpful Links

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

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

✅ You can merge normally! (2 Unrelated Failures)

As of commit 86ecd6b with merge base d987a6f (image):

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

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.

PaliC added a commit that referenced this pull request Jul 16, 2025
@PaliC PaliC requested a review from albanD July 16, 2025 06:15
@PaliC
Copy link
Contributor Author

PaliC commented Jul 16, 2025

@pytorchbot label "topic: not user facing"

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Jul 16, 2025
[ghstack-poisoned]
PaliC added a commit that referenced this pull request Jul 16, 2025
…ter is in use"


This PR makes some less risky changes to PyObjectSlot as there is a lot of stuff we do not need since there is only one interpreter. Specifically `check_interpreter` and `has_pyobj_nonhermetic` are removed


[ghstack-poisoned]
Copy link
Collaborator

@albanD albanD left a comment

Choose a reason for hiding this comment

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

Nice!

@PaliC
Copy link
Contributor Author

PaliC commented Jul 16, 2025

@pytorchbot merge -i

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jul 16, 2025
@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 16 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

@PaliC
Copy link
Contributor Author

PaliC commented Jul 16, 2025

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 16 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

[ghstack-poisoned]
@pytorchmergebot
Copy link
Collaborator

Rebased gh/PaliC/19/orig onto refs/remotes/origin/main because #158427 was rebased, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/158407)

saienduri pushed a commit to saienduri/pytorch that referenced this pull request Jul 22, 2025
… is in use (pytorch#158407)"

This reverts commit d9426a8.

Reverted pytorch#158407 on behalf of https://github.com/ZainRizvi due to Sorry but this is breaking internally, see D78496147 for details. To validate your fixes internally, you can follow the instructions here: https://fburl.com/fixing-ghfirst-reverts ([comment](pytorch#158288 (comment)))
[ghstack-poisoned]
PaliC added a commit that referenced this pull request Jul 23, 2025
@PaliC
Copy link
Contributor Author

PaliC commented Jul 23, 2025

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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

Merge failed

Reason: 1 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

@PaliC
Copy link
Contributor Author

PaliC commented Jul 23, 2025

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 2 checks: pull / linux-jammy-py3_9-clang9-xla / test (xla, 1, 1, linux.12xlarge, unstable), pull / linux-jammy-cuda12.8-py3.10-gcc11-test / test (distributed, 2, 3, linux.g4dn.12xlarge.nvidia.gpu)

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 added a commit that referenced this pull request Jul 25, 2025
… is in use (#158407)"

This reverts commit 255c054.

Reverted #158407 on behalf of https://github.com/ZainRizvi due to Reverting as per offline discussion to fix internal breaks.  @PaliC will reland this as a codev diff. Instructions here: https://fburl.com/fixing-ghfirst-reverts ([comment](#158288 (comment)))
@pytorchmergebot
Copy link
Collaborator

@PaliC your PR has been reverted as part of the stack under #158288.

@mikaylagawarecki mikaylagawarecki removed their request for review July 25, 2025 18:12
…ter is in use"


This PR makes some less risky changes to PyObjectSlot as there is a lot of stuff we do not need since there is only one interpreter. Specifically `check_interpreter` and `has_pyobj_nonhermetic` are removed


[ghstack-poisoned]
PaliC added a commit that referenced this pull request Jul 26, 2025
[ghstack-poisoned]
PaliC added a commit that referenced this pull request Jul 29, 2025
@PaliC
Copy link
Contributor Author

PaliC commented Jul 29, 2025

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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

yangw-dev pushed a commit that referenced this pull request Aug 1, 2025
… is in use (#158407)"

This reverts commit 255c054.

Reverted #158407 on behalf of https://github.com/ZainRizvi due to Reverting as per offline discussion to fix internal breaks.  @PaliC will reland this as a codev diff. Instructions here: https://fburl.com/fixing-ghfirst-reverts ([comment](#158288 (comment)))
yangw-dev pushed a commit that referenced this pull request Aug 1, 2025
…se (#158407)

This PR makes some less risky changes to PyObjectSlot as there is a lot of stuff we do not need since there is only one interpreter. Specifically `check_interpreter` and `has_pyobj_nonhermetic` are removed

Pull Request resolved: #158407
Approved by: https://github.com/albanD
ghstack dependencies: #158290, #158291
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-no-td Do not run TD on this PR ciflow/trunk Trigger trunk jobs on your pull request Merged Reverted topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants