Skip to content

CI: switch hardcoded Azure scale-set runners to AWS (interim) - #10991

Draft
amd-justchen wants to merge 1 commit into
developfrom
users/justchen/interim-aws-runners
Draft

CI: switch hardcoded Azure scale-set runners to AWS (interim)#10991
amd-justchen wants to merge 1 commit into
developfrom
users/justchen/interim-aws-runners

Conversation

@amd-justchen

Copy link
Copy Markdown
Contributor

CI: switch hardcoded Azure scale-set runners to AWS (interim)

Why

Multi-arch CI is moving to therock-ci-config
as the single source of truth for runner scale-set / label selection. That rollout is
still in progress, so several workflows in this repo still hardcode the legacy Azure
runner labels in runs-on: (or in workflow_call input defaults).

As an interim step -- until these workflows are driven by therock-ci-config -- this PR
repoints those hardcoded Azure labels at the equivalent AWS pools that the config repo
already treats as the production default. Linux CI has already been validated on the AWS
-prod pool, and Windows CI on the AWS mixed pool (-prod-mix) has been shown to be
cache-healthy and at hardware parity with the previous runners.

Label mapping (from therock-ci-config runner-config.json)

Legacy Azure label AWS label (interim) Notes
azure-linux-scale-rocm aws-linux-scale-rocm-prod linux.default AWS pool
azure-windows-scale-rocm aws-windows-scale-rocm-prod-mix windows.default AWS pool (mixed EPYC pool)
azure-*-heavy* aws-linux-scale-rocm-large none present in this repo -- no change needed

No *-heavy* / ramdisk Azure variants exist in this repo, so the heavy -> -large
mapping did not apply.

Changes

  • .github/workflows/hip-nvidia-ci.yml -- runs-on -> aws-linux-scale-rocm-prod
  • .github/workflows/rocjitsu-corpus-tests.yml -- runs-on -> aws-linux-scale-rocm-prod
  • .github/workflows/rocprofiler-sdk-codeql.yml -- runs-on -> aws-linux-scale-rocm-prod
  • .github/workflows/rocprofiler-sdk-build-ci-docker-images.yml -- runs-on -> aws-linux-scale-rocm-prod
  • .github/workflows/therock-ci-linux.yml -- build_runs_on input default -> aws-linux-scale-rocm-prod
  • .github/workflows/therock-build-linux.yml -- build_runs_on input default -> aws-linux-scale-rocm-prod
  • .github/workflows/therock-ci-windows.yml -- build_runs_on input default -> aws-windows-scale-rocm-prod-mix
  • .github/workflows/therock-test-packages.yml -- comment reference updated for accuracy (no behavior change)

Rollback

Revert this PR (restores the azure-*-scale-rocm labels). No config-repo change is
required either way; this is purely a hardcoded-label switch pending full therock-ci-config
adoption.

Repoint hardcoded azure-*-scale-rocm runner labels to the equivalent AWS
pools (aws-linux-scale-rocm-prod / aws-windows-scale-rocm-prod-mix) per
therock-ci-config, as an interim step until the multi-arch CI workflows
select runners via therock-ci-config. No *-heavy* Azure variants exist in
this repo, so the heavy -> -large mapping did not apply.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@amd-justchen

Copy link
Copy Markdown
Contributor Author

Companion PR (same interim Azure->AWS runner switch) in rocm-libraries: ROCm/rocm-libraries#11502

@therock-pr-bot

therock-pr-bot Bot commented Aug 31, 2026

Copy link
Copy Markdown

❌ PR Check — Action Required

Check Status Details
📝 PR Description ❌ Fail 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
JIRA ID (on separate line)
ROCM-25757
ISSUE ID : TESTUTO-3334
ISSUE ID #3334
ISSUE ID - TESTAUTO-3433
ISSUE ID (on separate line)
AIRUNTIME-2352
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 ✅ Pass
🚫 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 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.

🙋 Wish to Override Policy?

@therock-pr-bot

Copy link
Copy Markdown

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

  • ❌ PR Description

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

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.

1 participant