Skip to content

Conversation

@pragupta
Copy link
Collaborator

#2110)

When timing in enabled, ROCR runtime used to sleep for a small amount which ensured that the application saw the correct state. However, for perf reasons this sleep was removed and now the state is not guaranteed to be "started". That's why, I updated the test state check to be either "started" or "scheduled"

Fixes https://ontrack-internal.amd.com/browse/SWDEV-525883

Upstream PR: pytorch#153545

(cherry picked from commit 8a1ad2c)

Fixes #ISSUE_NUMBER

pragupta and others added 2 commits May 28, 2025 14:46
…OCm#2110)

When timing in enabled, ROCR runtime used to sleep for a small amount
which ensured that the application saw the correct state. However, for
perf reasons this sleep was removed and now the state is not guaranteed
to be "started". That's why, I updated the test state check to be either
"started" or "scheduled"

Fixes https://ontrack-internal.amd.com/browse/SWDEV-525883

Upstream PR: pytorch#153545

(cherry picked from commit 8a1ad2c)
@pruthvistony pruthvistony merged commit 77a7b6c into ROCm:release/2.7 May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants