Skip to content

[WIP][rocjitsu] Add CI workflow (pip rocm-sdk-core approach)#6479

Draft
newling wants to merge 1 commit into
ROCm:developfrom
newling:rocjitsu-ci-pip
Draft

[WIP][rocjitsu] Add CI workflow (pip rocm-sdk-core approach)#6479
newling wants to merge 1 commit into
ROCm:developfrom
newling:rocjitsu-ci-pip

Conversation

@newling
Copy link
Copy Markdown
Contributor

@newling newling commented May 27, 2026

Summary

Alternative to #6448 (apt approach), using pip install rocm-sdk-core instead of apt install rocm-hip-sdk. Addresses review feedback from #6448.

See also #6441 (earlier pip attempt, closed).

Changes from #6448

  • ROCm installed via pip (~6s) instead of apt (~4min)
  • Pinned actions/checkout to SHA per best practice
  • Use -DCMAKE_CXX_COMPILER instead of env vars

Test plan

  • CI builds rocjitsu successfully
  • HIP device kernel tests compile and run
  • All non-RocminfoTest tests pass

@github-actions github-actions Bot added the github actions Pull requests that update GitHub Actions code label May 27, 2026
newling added a commit to newling/rocm-systems that referenced this pull request May 27, 2026
Before this PR, the TheRock CI builds rocjitsu (as part of
THEROCK_ENABLE_EMULATION) but does not run its tests — rocjitsu
is not in repos-config.json. The only rocjitsu-specific CI is
pre-commit formatting.

After this PR, every PR touching emulation/rocjitsu/ gets a
dedicated job that builds rocjitsu and runs its full ctest suite
(~450 tests), including HIP integration tests (memcpy,
vector_add, matmul). No GPU hardware needed — tests run on the
built-in CPU emulator. ROCm installed from the AMD apt repo for
hipcc and device libraries.

RocminfoTest excluded (requires /dev/kfd, unavailable on CI).

Related: ROCm#6479
(alternative using pip rocm-sdk-core)
@newling newling force-pushed the rocjitsu-ci-pip branch 3 times, most recently from 8cdc7b4 to fe5a321 Compare May 27, 2026 19:11
@newling newling force-pushed the rocjitsu-ci-pip branch 3 times, most recently from 0184d9e to 13e3c7d Compare May 27, 2026 19:52
Before this PR, the TheRock CI builds rocjitsu (as part of
THEROCK_ENABLE_EMULATION) but does not run its tests — rocjitsu
is not in repos-config.json. The only rocjitsu-specific CI is
pre-commit formatting.

After this PR, every PR touching emulation/rocjitsu/ gets a
dedicated job that builds rocjitsu and runs its full ctest suite
(~450 tests), including HIP integration tests (memcpy,
vector_add, matmul). No GPU hardware needed — tests run on the
built-in CPU emulator. ROCm SDK installed via pip from TheRock.

Decouple HIP test cmake gate from HSA_RUNTIME64 — the HIP tests
only need hipcc for compilation and LD_PRELOAD at runtime.

Prefer ROCM_PATH from env over deriving from compiler location
in rj_add_device_kernel, for pip SDK compatibility.

RocminfoTest excluded (requires /dev/kfd, unavailable on CI).

Related PRs:
- ROCm#6448: alternative approach using ROCm apt packages
- ROCm#6441: earlier pip attempt (closed)
@newling newling force-pushed the rocjitsu-ci-pip branch from 13e3c7d to bcabc62 Compare May 27, 2026 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

github actions Pull requests that update GitHub Actions code organization: ROCm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant