-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Solid XPU UT test_memory_allocation #141325
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/141325
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 2 New FailuresAs of commit e763e96 with merge base 2b39a8d ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
The failure |
|
"Unrelated failures" |
Merge startedYour change will be merged while ignoring the following 2 checks: xpu / win-vs2022-xpu-py3 / build, linux-binary-manywheel / manywheel-py3_9-cuda12_6-test / test Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
# Motivation Fix pytorch#141326 # Additional Context We use the previous value queried by these APIs as the reference value rather than 0. With this PR, we don't depend on the Python garbage collection mechanism anymore. Pull Request resolved: pytorch#141325 Approved by: https://github.com/EikanWang
Stack from ghstack (oldest at bottom):
Motivation
Fix #141326
Additional Context
We use the previous value queried by these APIs as the reference value rather than 0. With this PR, we don't depend on the Python garbage collection mechanism anymore.
cc @gujinghui @EikanWang @fengyuan14