Skip to content

[CI] Exclude nvidia-cuda-cccl from the ROCm test lockfile - #1412

Merged
eble-amd merged 1 commit into
gfx11from
zohaibm.rocm-lockfile-exclude-cccl
Oct 28, 2026
Merged

eble-amd merged 1 commit into
gfx11from
zohaibm.rocm-lockfile-exclude-cccl

Conversation

@zohaibm-amd

Copy link
Copy Markdown

Overview

Port of vllm-project#64302 to gfx11. The pip-compile-rocm pre-commit hook currently fails on every PR against gfx11 (for example #1411), because CI's regeneration of requirements/test/rocm.txt no longer matches the committed file.

Root cause: torch 2.15.0 reached PyPI on 2026-10-28 (15:16 UTC). The ROCm test lockfile resolves torch and its CUDA dependencies from PyPI only to exclude them via --no-emit-package. The new torch moves those dependencies to CUDA 13.2, where nvidia-nvshmem-cu13 3.7.2 depends on nvidia-cuda-cccl. That package was not on the exclude list, so it leaked into the ROCm lockfile, and nvidia-curand dropped out of the resolution.

Changes

  • .pre-commit-config.yaml: add --no-emit-package nvidia-cuda-cccl to pip-compile-rocm. This is the same line as upstream; that part cherry-picks cleanly.
  • requirements/test/rocm.txt: regenerated with the hook using its pinned uv 0.11.1, rather than taking upstream's lockfile hunk, which does not apply because the gfx11 lockfile has diverged. The only changes are the embedded command line and the excluded-package comment list (+nvidia-cuda-cccl, -nvidia-curand). No pinned versions change.

Validation

pip-compile-rocm passes locally on this commit. The lockfile tracks what PyPI serves, so a later upstream release could require regenerating it again.

Signed-off-by: Zohaib Moti <zohaib.moti@amd.com>
@eble-amd
eble-amd merged commit e3f75cd into gfx11 Oct 28, 2026
10 checks passed
@eble-amd
eble-amd deleted the zohaibm.rocm-lockfile-exclude-cccl branch October 28, 2026 20:49
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