Skip to content

[release/2.13][ROCm] Use rocm-sdk-devel as ROCM_HOME for TheRock installs - #3620

Closed
ethanwee1 wants to merge 2 commits into
release/2.13from
ethanwee/rocm-sdk-devel-rocm-home-2.13
Closed

ethanwee1 wants to merge 2 commits into
release/2.13from
ethanwee/rocm-sdk-devel-rocm-home-2.13

Conversation

@ethanwee1

@ethanwee1 ethanwee1 commented Sep 9, 2026

Copy link
Copy Markdown

Problem

QA 2.13 Docker images fail four TestMemPool tests because load_inline
builds dummy_allocator with -isystem …/_rocm_sdk_core/include. Devel is
already installed; torch never puts it on the include path. Tracked in
ROCM-30466.

PyTorch ROCm CI exports ROCM_HOME from rocm-sdk path --root, so it never
hits Guess #2.

Changes

Backport of pytorch#195726: _find_rocm_home() prefers
_rocm_sdk_devel over _rocm_sdk_core via find_spec. Adds TestFindRocmHome
so CI covers Guess #2 with the env unset.

Validation

Equivalent 2.14 QA image (container rocm30466), env unset: four TestMemPool
tests FAILED (errors=4) unpatched, OK patched. Same _find_rocm_home hunk.

TestFindRocmHome in that container, 3/3 passed in 4.667s (devel-over-core,
core fallback, env wins).

Upstream: pytorch#195726

…alls

JIT load_inline against TheRock wheels was resolving ROCM_HOME to
runtime-only _rocm_sdk_core, so hipBLAS headers in _rocm_sdk_devel
were never on the include path. Prefer devel via find_spec.
… core

Trunk ROCm CI exports ROCM_HOME, so TestMemPool never hits Guess #2.
Mock find_spec with both packages and the env unset so CI covers the
TheRock JIT include path.
@ethanwee1

Copy link
Copy Markdown
Author

Superseded by #3635 (the functional fix, already merged). Tests-only follow-up for trunk is pytorch#197449.

@ethanwee1 ethanwee1 closed this Sep 17, 2026
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.

1 participant