Skip to content

[proxy_tensor] Do not clobber tensor proxies for inplace ops #155456

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

Open
wants to merge 2 commits into
base: gh/IvanKobzarev/115/base
Choose a base branch
from

Conversation

IvanKobzarev
Copy link
Contributor

@IvanKobzarev IvanKobzarev commented Jun 9, 2025

Copy link

pytorch-bot bot commented Jun 9, 2025

🔗 Helpful Links

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

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

❌ 51 New Failures, 1 Unrelated Failure

As of commit a9002d6 with merge base 75f258d (image):

NEW FAILURES - The following jobs have 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 pytorch-bot bot added ciflow/inductor release notes: fx release notes category labels Jun 9, 2025
IvanKobzarev added a commit that referenced this pull request Jun 9, 2025
ghstack-source-id: 8a6e1cc
Pull Request resolved: #155456
@IvanKobzarev IvanKobzarev added the topic: not user facing topic category label Jun 9, 2025
@ezyang
Copy link
Contributor

ezyang commented Jun 10, 2025

PR desc?

cc ezyang SherlockNoMad EikanWang jgong5 wenzhe-nrv

[ghstack-poisoned]
IvanKobzarev added a commit that referenced this pull request Jun 11, 2025
@IvanKobzarev IvanKobzarev changed the title [proxy_tensor] Do not clobber tensor proxies [proxy_tensor] Do not clobber tensor proxies for inplace ops Jun 11, 2025
@IvanKobzarev
Copy link
Contributor Author

PR desc?

Sorry, just testing so far the CI which tests will fail.

Copy link
Contributor

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 Aug 10, 2025
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.

3 participants