Skip to content

ci: add gfx125x to TheRock CI matrix - #217

Open
dan-garvey wants to merge 1 commit into
ROCm:amd-stagingfrom
dan-garvey:users/dan-garvey/gfx125x-therock-ci
Open

ci: add gfx125x to TheRock CI matrix#217
dan-garvey wants to merge 1 commit into
ROCm:amd-stagingfrom
dan-garvey:users/dan-garvey/gfx125x-therock-ci

Conversation

@dan-garvey

Copy link
Copy Markdown

Summary

  • add gfx125X-dcgpu to the ROCgdb TheRock CI build matrix

This keeps gfx125X-dcgpu build-only because the existing test job remains gated to gfx94X-dcgpu.

Depends on ROCm/therock-ci-config#14.

Testing

  • parsed .github/workflows/therock-ci.yml and .github/workflows/therock-ci-linux.yml with PyYAML
  • git diff --check

@dan-garvey
dan-garvey requested a review from a team as a code owner July 16, 2026 22:49
@lumachad

Copy link
Copy Markdown
Collaborator

@dan-garvey Do you have an ETA on when we can switch to also running tests on gfx1250? And could we enable gfx950 testing by default?

@lumachad lumachad self-assigned this Jul 22, 2026
@lumachad

Copy link
Copy Markdown
Collaborator

@dan-garvey We use rebase and merge for ROCgdb. Due to that, could you please add a commit message, as the PR description will be discarded when merging.

@lumachad

Copy link
Copy Markdown
Collaborator

@dan-garvey ping?

@lumachad

lumachad commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Converting to draft as we don't seem to have any activity.

@lumachad
lumachad marked this pull request as draft August 6, 2026 10:57
@lumachad lumachad assigned dan-garvey and unassigned lumachad Aug 6, 2026
Add gfx125X-dcgpu to the ROCgdb TheRock CI matrix so the project builds
Linux packages for that target.

Keep test execution limited to gfx94X-dcgpu; the gfx125X-dcgpu job
remains build-only until test hardware is available.

Depends on ROCm/therock-ci-config#14.
@dan-garvey
dan-garvey force-pushed the users/dan-garvey/gfx125x-therock-ci branch from 4cd22b7 to 870e819 Compare August 6, 2026 16:22
@dan-garvey
dan-garvey marked this pull request as ready for review August 7, 2026 22:26
@dan-garvey

Copy link
Copy Markdown
Author

I dont have any context on 950 capacity/usage/roadmap, so I'll leave that as out of scope for this PR.

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