Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move CI large runners to free runners #189

Open
marcoieni opened this issue Jan 14, 2025 · 0 comments
Open

Move CI large runners to free runners #189

marcoieni opened this issue Jan 14, 2025 · 0 comments
Assignees

Comments

@marcoieni
Copy link
Member

marcoieni commented Jan 14, 2025

What

We want to optimize the resources used by our CI.

We already migrated many large runners to free runners by splitting tests into multiple jobs. E.g. rust-lang/rust#134124

How

In the following we analyze what jobs of the auto branch we haven't moved yet and why.

Here's a list of all large runners, together with the jobs that are still using them and their average cost:

  • job-aarch64-linux:
    • aarch64-gnu:
      There are no free runners for linux arm. GitHub plans to make them available in Q1 2025.
    • aarch64-gnu-debug:
      Same motivation as aarch64-gnu 👆
  • job-linux-8c:
    • dist-arm-linux:
      Moving this job to a free runner makes it too slow. We haven't investigated if it's possible to split dist jobs yet.
    • x86_64-fuchsia:
      I tried to convert this job to free runners here but it was too slow. This job can't be parallelized because it is just a build.
    • x86_64-gnu-distcheck:
      I tried to convert this job to free runners here but it was too slow. This job can't be parallelized because it only runs one task (distcheck). Maybe it can be parallelized but it's not trivial.
  • job-linux-4c-largedisk:
  • job-linux-16c:
    • dist-x86_64-linux:
      Same motivation as dist-arm-linux.
    • dist-x86_64-linux-alt:
      Same motivation as dist-arm-linux.
  • job-windows-8c:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant