ci: [TEST] use larger runners for compilation-heavy jobs#7038
Open
huth-stacks wants to merge 3 commits into
Open
ci: [TEST] use larger runners for compilation-heavy jobs#7038huth-stacks wants to merge 3 commits into
huth-stacks wants to merge 3 commits into
Conversation
|
|
Author
|
4 tasks
Switch nextest-archive, cargo-hack native-targets, and constants-check to ubuntu-latest-m (4 vCPU, 16GB RAM) for faster compilation. The release workflow already uses these runners. Expected ~30-50% faster compilation with negligible cost difference.
huth-stacks
force-pushed
the
ci/P3-larger-runners
branch
from
d475be2 to
feba8c5
Compare
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
2 participants
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.
DO NOT MERGE — Test PR for CI timing validation
This PR exists solely to validate the impact of larger runners on CI compilation jobs.
It cannot be tested on a personal fork because
ubuntu-latest-mrunners are onlyavailable on org accounts with GitHub Team/Enterprise plans.
This PR will be closed after timing data is collected.
What
Switch three compilation-heavy CI jobs from
ubuntu-latest(2 vCPU, 7GB RAM) toubuntu-latest-m(4 vCPU, 16GB RAM).Why
Rust compilation is CPU-bound. These three jobs are the longest-running compilation tasks:
The release workflow (
release-build.yml) already usesubuntu-latest-m, confirmingthese runners are available to the org.
The Change
One word change in each of 3 files (
ubuntu-latest→ubuntu-latest-m):.github/workflows/create-cache.yml: nextest-archive job.github/workflows/cargo-hack-check.yml: native-targets job.github/workflows/constants-check.yml: check-consts job3 lines changed across 3 files. Other jobs untouched.
Metrics to Collect
Security Checklist