KEMBAR78
Fix xpu memory stats error by guangyey · Pull Request #135818 · pytorch/pytorch · GitHub
Skip to content

Conversation

@guangyey
Copy link
Collaborator

@guangyey guangyey commented Sep 12, 2024

Stack from ghstack (oldest at bottom):

Motivation

fix #135726
After merging two free blocks, I made a stupid mistake of ignoring the correct size to decrease the active memory size, which should be the original block size instead of the merged block size.

Additional Context

Add a UT to guard this scenario.

cc @gujinghui @EikanWang @fengyuan14

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 12, 2024

🔗 Helpful Links

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

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

❌ 1 New Failure, 6 Cancelled Jobs, 1 Unrelated Failure

As of commit 8ad0512 with merge base f5f1d0a (image):

NEW FAILURE - The following job has failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

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

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

@guangyey guangyey changed the title fix xpu memory stats error Fix xpu memory stats error Sep 12, 2024
@guangyey guangyey added ciflow/xpu Run XPU CI tasks ciflow/trunk Trigger trunk jobs on your pull request topic: bug fixes topic category labels Sep 12, 2024
@guangyey guangyey added module: xpu Intel XPU related issues topic: not user facing topic category labels Sep 12, 2024
guangyey added a commit that referenced this pull request Sep 12, 2024
ghstack-source-id: 89f32e0
Pull Request resolved: #135818
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
@guangyey
Copy link
Collaborator Author

Unrelated failure.
@pytorchbot merge -i

Chao1Han pushed a commit to Chao1Han/pytorch that referenced this pull request Sep 20, 2024
# Motivation
fix pytorch#135726
After merging two free blocks, I made a stupid mistake of ignoring the correct size to decrease the active memory size, which should be the original block size instead of the merged block size.

# Additional Context
Add a UT to guard this scenario.

Pull Request resolved: pytorch#135818
Approved by: https://github.com/EikanWang
guangyey added a commit that referenced this pull request Sep 23, 2024
# Motivation
fix #135726
After merging two free blocks, I made a stupid mistake of ignoring the correct size to decrease the active memory size, which should be the original block size instead of the merged block size.

# Additional Context
Add a UT to guard this scenario.

Pull Request resolved: #135818
Approved by: https://github.com/EikanWang

(cherry picked from commit e6b6835)
atalman pushed a commit that referenced this pull request Sep 24, 2024
# Motivation
fix #135726
After merging two free blocks, I made a stupid mistake of ignoring the correct size to decrease the active memory size, which should be the original block size instead of the merged block size.

# Additional Context
Add a UT to guard this scenario.

Pull Request resolved: #135818
Approved by: https://github.com/EikanWang

(cherry picked from commit e6b6835)
@github-actions github-actions bot deleted the gh/guangyey/69/head branch October 14, 2024 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request ciflow/xpu Run XPU CI tasks Merged module: xpu Intel XPU related issues open source topic: bug fixes topic category topic: not user facing topic category

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants