CI: switch hardcoded Azure scale-set runners to AWS (interim) - #10991
Draft
amd-justchen wants to merge 1 commit into
Draft
CI: switch hardcoded Azure scale-set runners to AWS (interim)#10991amd-justchen wants to merge 1 commit into
amd-justchen wants to merge 1 commit into
Conversation
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>
Contributor
Author
|
Companion PR (same interim Azure->AWS runner switch) in rocm-libraries: ROCm/rocm-libraries#11502 |
❌ PR Check — Action Required
📖 Need help? See the Policy FAQ for details on every check and how to fix failures. |
|
🚫 Please fix the failed policies before requesting reviews. The following policy checks failed:
The |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 inworkflow_callinput 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
-prodpool, and Windows CI on the AWS mixed pool (-prod-mix) has been shown to becache-healthy and at hardware parity with the previous runners.
Label mapping (from therock-ci-config
runner-config.json)azure-linux-scale-rocmaws-linux-scale-rocm-prodazure-windows-scale-rocmaws-windows-scale-rocm-prod-mixazure-*-heavy*aws-linux-scale-rocm-largeNo
*-heavy*/ ramdisk Azure variants exist in this repo, so the heavy ->-largemapping 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_oninput default ->aws-linux-scale-rocm-prod.github/workflows/therock-build-linux.yml--build_runs_oninput default ->aws-linux-scale-rocm-prod.github/workflows/therock-ci-windows.yml--build_runs_oninput 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-rocmlabels). No config-repo change isrequired either way; this is purely a hardcoded-label switch pending full therock-ci-config
adoption.