Skip to content

[ci] Add MI455 (gfx125X) bringup to multi-arch CI#7983

Merged
geomin12 merged 4 commits into
developfrom
users/geomin12/mi455-bringup
Jun 30, 2026
Merged

[ci] Add MI455 (gfx125X) bringup to multi-arch CI#7983
geomin12 merged 4 commits into
developfrom
users/geomin12/mi455-bringup

Conversation

@geomin12

@geomin12 geomin12 commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Configure gfx125X-dcgpu for rocm-systems nightly multi-arch CI with:

  • Custom test runner: linux-mi455-gpu-rocm
  • Limited tests: hip-tests, rocrtst, sanity only
  • Uses TheRock branch with external_family_overrides support

working here: https://github.com/ROCm/rocm-systems/actions/runs/28422102951

Configure gfx125X-dcgpu for rocm-systems nightly multi-arch CI with:
- Custom test runner: linux-mi455-gpu-rocm
- Limited tests: hip-tests, rocrtst, sanity only
- Uses TheRock branch with external_family_overrides support

TEMPORARY: Points to users/geomin12/mi455-bringup branch in TheRock.
TODO(geomin12): Revert to main once MI455 is in therock-ci-config.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot added the github actions Pull requests that update GitHub Actions code label Jun 29, 2026
@therock-pr-bot

Copy link
Copy Markdown

❌ PR Check — Action Required

Check Status Details
🌿 Branch Name ✅ Pass
📝 PR Title/Description ❌ Fail Error: Title does not follow Conventional Commits style.
Expected: start with a valid type (feat, fix, docs, …).
Desired format: type(optional-scope): short description
───
Error: PR description must reference a JIRA ID, ISSUE ID, or a GitHub closing keyword.
Expected: include a JIRA ID / ISSUE ID line (separator : or -, or omitted; value may be a JIRA key, a number with/without #, or a link), OR a closing keyword + issue reference. Accepted examples:
JIRA ID : TESTAUTO-6039
JIRA ID - #330
JIRA ID #330
ISSUE ID : TESTUTO-3334
ISSUE ID #3334
ISSUE ID - TESTAUTO-3433
ISSUE ID : https://github.com/<org_name>/<repo_name>/issues/1234
Closes #10
Fixes octo-org/octo-repo#100
Resolves: #123
#123
https://github.com/<org_name>/<repo_name>/issues/123
Current: no valid JIRA/ISSUE/closing-keyword reference found
Forbidden Files ✅ Pass
🧪 Unit Test ✅ Pass PR does not contain code files — Unit Test auto-passed
🔎 pre-commit ⏳ Pending ⏳ Still running…
🚫 Draft PR 🔜 To Be Enabled
🚩 Feature Flag 🔜 To Be Enabled
📊 Code Coverage 🔜 To Be Enabled

⚠️ 1 policy check(s) failed. Please address the issues above before this PR can be Reviewed.

🚫 Please fix the failed policies

  • ❌ PR Title/Description

The Not ready to Review label was added to this PR. Once all policies pass, the label is removed automatically.

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

@therock-pr-bot

Copy link
Copy Markdown

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

  • ❌ PR Title/Description

The Not ready to Review label has been added to this PR.
Once all policies pass, the label will be removed automatically.

@rahulc-gh rahulc-gh left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you moving to therock ref to your private branch ??
Also we cannot gfx125x until ROCm/TheRock#6082 lands , else your pytorch buidl will be attempted for 2.10 and 2.12 torch branches and it will fail.

@geomin12

geomin12 commented Jun 30, 2026

Copy link
Copy Markdown
Contributor Author

Why are you moving to therock ref to your private branch ?? Also we cannot gfx125x until ROCm/TheRock#6082 lands , else your pytorch buidl will be attempted for 2.10 and 2.12 torch branches and it will fail.

this nightly behaves differently than TheRock nightly. this is just build and test signal! no releases here

@rahulc-gh rahulc-gh left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just move theRock ref to main before merging. If it sjust build and test with no pytorch this can be merged for gfx125x as well builds should be good.

@geomin12 geomin12 marked this pull request as ready for review June 30, 2026 05:46
@geomin12 geomin12 requested a review from a team as a code owner June 30, 2026 05:46
@geomin12

Copy link
Copy Markdown
Contributor Author

landing this to get mi455 coverage

@geomin12 geomin12 merged commit dbb020a into develop Jun 30, 2026
6 of 9 checks passed
@geomin12 geomin12 deleted the users/geomin12/mi455-bringup branch June 30, 2026 05:48
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 Not ready to Review organization: ROCm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants