-
Notifications
You must be signed in to change notification settings - Fork 608
[ET-VK][ez] Make sure vTensor is not referencing the global context #9458
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
Conversation
## 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-poisoned]
## 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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/9458
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New FailuresAs of commit 1f4b46a with merge base ea43453 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D71560884 |
This PR needs a
|
246c3d8
into
gh/SS-JIA/198/base
…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: #9458
…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
…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
Stack from ghstack (oldest at bottom):
Context
Some functions in
vTensor
accidentally referenced the global context by callingcontext()
; the correct thing to do is to use the context pointer associated with thevTensor
by usingstorage_.context_
instead.Differential Revision: D71560884