ci: use arm runners for guix

[PastaPastaPasta]

Issue being fixed or feature implemented

(At least currently, in public beta, maybe they'll be worse when more congested) Arm runners appear about 20% faster.

What was done?

Use arm64 runners for guix instead of x86.

How Has This Been Tested?

Udjin's patch recently: https://github.com/UdjinM6/dash/actions/runs/13187795136
vs this commit: (with his as well)
https://github.com/PastaPastaPasta/dash/actions/runs/13188732140

Breaking Changes

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

[coderabbitai]

Walkthrough

The pull request updates the build workflow configuration by changing the job environment. The operating system for both the build-image and build jobs is now set to run on ubuntu-24.04-arm instead of the previously used ubuntu-latest. No changes were made to the individual steps within the jobs—such as the checkout process, Docker setup, variable preparation, authentication to the GitHub Container Registry, image building, caching, or artifact uploading. The overall structure and sequence of operations within the workflow remain unchanged, with the only adjustment being the specific environment configuration for executing the jobs.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96dd126 and 04a322c.

📒 Files selected for processing (1)

• .github/workflows/guix-build.yml (2 hunks)

🧰 Additional context used

🪛 actionlint (1.7.4)

.github/workflows/guix-build.yml

14-14: label "ubuntu-24.04-arm" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

---

67-67: label "ubuntu-24.04-arm" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: Build (linux64_ubsan, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_tsan, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_sqlite, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_nowallet, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_fuzz, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_cxx20, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (arm-linux, arm-linux-gnueabihf, arm-linux)

🔇 Additional comments (2)

.github/workflows/guix-build.yml (2)

67-67: Runner Label Update in build Job
The "runs-on" field for the build job is now set to "ubuntu-24.04-arm", which—like in the build-image job—is flagged by static analysis as an unknown label. Please review your runner configuration: if you are targeting ARM architectures with a custom runner, ensure that the custom label is properly registered in your actionlint configuration; otherwise, consider switching to a supported label such as "ubuntu-24.04".

A possible diff for using a standard label is:

-    runs-on: ubuntu-24.04-arm
+    runs-on: ubuntu-24.04

✅ Verification successful

Action Required: Update Runner Configuration/Label
The static analysis correctly flags the use of "ubuntu-24.04-arm" as an unknown label. If you're targeting ARM architectures with a custom runner, please ensure that the label is properly registered in your actionlint configuration. Otherwise, it’s recommended to switch to a standard, supported label such as "ubuntu-24.04".

• Confirm whether a custom ARM runner is intended for this job.
• If not, update the "runs-on" field to "ubuntu-24.04" per the provided diff.

🧰 Tools

🪛 actionlint (1.7.4)

67-67: label "ubuntu-24.04-arm" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

---

14-14: Runner Label Update in build-image Job
The update changes the runner from a generic label to "ubuntu-24.04-arm". However, according to the static analysis hints, "ubuntu-24.04-arm" is not recognized among the available runner labels. Consider verifying whether this is a custom label configured on your self-hosted runners or if you meant to use an officially supported label such as "ubuntu-24.04".

A suggested diff if you intended to use an officially recognized label:

-    runs-on: ubuntu-24.04-arm
+    runs-on: ubuntu-24.04

🧰 Tools

🪛 actionlint (1.7.4)

14-14: label "ubuntu-24.04-arm" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[UdjinM6]

To provide a bit more context: https://github.blog/changelog/2024-06-24-github-actions-ubuntu-24-04-image-now-available-for-arm64-runners/

The repo for these new images is https://github.com/actions/partner-runner-images

[UdjinM6]

https://github.com/UdjinM6/dash/actions/runs/13196102514

ACK 04a322c

[kwvg]

utACK 04a322c