fix(ci): Pass build_runs_on to multi_arch_build_portable_linux.yml#6069
Merged
Conversation
The multi_arch_release_linux.yml workflow was missing the build_runs_on parameter when calling multi_arch_build_portable_linux.yml, causing ASAN builds to use the default runner (azure-linux-scale-rocm) instead of the sanitizer runner (azure-linux-scale-rocm-heavy-ramdisk) selected by configure_multi_arch_ci.py. This resulted in AWS IAM permission errors since the AWS runner role lacks permissions to the therock-dev-artifacts bucket. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
✅ All Checks Passed — Ready for Review
📖 Need help? See the Policy FAQ for details on every check and how to fix failures. |
|
🎉 All checks passed! This PR is ready for review. |
nunnikri
approved these changes
Jun 23, 2026
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.
The multi_arch_release_linux.yml workflow was missing the build_runs_on parameter when calling multi_arch_build_portable_linux.yml, causing ASAN builds to use the default runner (azure-linux-scale-rocm) instead of the sanitizer runner (azure-linux-scale-rocm-heavy-ramdisk) selected by configure_multi_arch_ci.py.
This resulted in AWS IAM permission errors since the AWS runner role lacks permissions to the therock-dev-artifacts bucket.
Tested here: https://github.com/ROCm/TheRock/actions/runs/28047796953/job/83030388981#step:1:2 and properly passing it in
Tested here too: https://github.com/ROCm/TheRock/actions/runs/28039559307/job/83001994909#step:3:51
ISSUE ID #5937