Skip to content

Comments

tools: switch to ARM runners on GHA jobs#61903

Open
aduh95 wants to merge 2 commits intonodejs:mainfrom
aduh95:ubuntu-latest
Open

tools: switch to ARM runners on GHA jobs#61903
aduh95 wants to merge 2 commits intonodejs:mainfrom
aduh95:ubuntu-latest

Conversation

@aduh95
Copy link
Contributor

@aduh95 aduh95 commented Feb 20, 2026

AFAICT those are slightly faster (this can be seen for e.g. test-linux and test-shared which run both varients, the ARM one always finishes first).
According to https://docs.github.com/en/billing/concepts/product-billing/github-actions#baseline-minute-costs, ARM runners are also cheaper – which is only relevant for the private repo where we prepare the security releases.

@aduh95 aduh95 added lts-watch-v20.x PRs that may need to be released in v20.x lts-watch-v22.x PRs that may need to be released in v22.x labels Feb 20, 2026
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/actions

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Feb 20, 2026
@aduh95 aduh95 changed the title tools: switch to ARM runners for non-slim ones tools: switch to ARM runners on GHA jobs Feb 20, 2026
@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Feb 20, 2026

The GitHub ARM images from https://github.com/actions/partner-runner-images tend to be less well supported and are not updated so often as the ones from https://github.com/actions/runner-images which are GitHub's own self-hosted runner images. The manifests for the Ubuntu ARM images lists no versions (see actions/partner-runner-images#79).

It is often difficult to get any response to the issue list on https://github.com/actions/partner-runner-images/issues

This may or may not be important to Node.js' actions. If it doesn't work out, you can swap back relatively easily I imagine.

@aduh95
Copy link
Contributor Author

aduh95 commented Feb 20, 2026

@MikeMcC399 that's good context, thanks for sharing, I didn't know there were a difference between how the two images are being maintained. That being said, I don't think it changes anything for us given that we:

  • never ever had to even interact with that issue tracker AFAIK.
  • can easily revert if need be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lts-watch-v20.x PRs that may need to be released in v20.x lts-watch-v22.x PRs that may need to be released in v22.x meta Issues and PRs related to the general management of the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants