Skip to content

[ET-VK][ez] Make sure vTensor is not referencing the global context #9469

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

Merged
merged 1 commit into from
Mar 20, 2025

Conversation

pytorchbot
Copy link
Collaborator

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #9458 by @SS-JIA
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/SS-JIA/198/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/SS-JIA/198/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/SS-JIA/198/orig
@diff-train-skip-merge

## Context

Some functions in `vTensor` accidentally referenced the global context by calling `context()`; the correct thing to do is to use the context pointer associated with the `vTensor` by using `storage_.context_` instead.

Differential Revision: [D71560884](https://our.internmc.facebook.com/intern/diff/D71560884/)

ghstack-source-id: 273023082
Pull Request resolved: #9458
@pytorchbot pytorchbot requested a review from SS-JIA as a code owner March 20, 2025 19:39
Copy link

pytorch-bot bot commented Mar 20, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure, 69 Pending

As of commit 4e4b1a1 with merge base ea43453 (image):

NEW FAILURE - The following job has failed:

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Mar 20, 2025
Copy link

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.

@kirklandsign kirklandsign merged commit 1300cda into main Mar 20, 2025
78 of 80 checks passed
@kirklandsign kirklandsign deleted the gh/SS-JIA/198/orig branch March 20, 2025 19:54
oscarandersson8218 pushed a commit to oscarandersson8218/executorch that referenced this pull request Mar 21, 2025
…ytorch#9469)

## Context

Some functions in `vTensor` accidentally referenced the global context by calling `context()`; the correct thing to do is to use the context pointer associated with the `vTensor` by using `storage_.context_` instead.

Differential Revision: [D71560884](https://our.internmc.facebook.com/intern/diff/D71560884/)

ghstack-source-id: 273023082
Pull Request resolved: pytorch#9458
DannyYuyang-quic pushed a commit to CodeLinaro/executorch that referenced this pull request Apr 2, 2025
…ytorch#9469)

## Context

Some functions in `vTensor` accidentally referenced the global context by calling `context()`; the correct thing to do is to use the context pointer associated with the `vTensor` by using `storage_.context_` instead.

Differential Revision: [D71560884](https://our.internmc.facebook.com/intern/diff/D71560884/)

ghstack-source-id: 273023082
Pull Request resolved: pytorch#9458
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants