ci: run Check on the dev runner label #63

Merged
Claude-Run merged 1 commit from ci/LINKS-29-check-dev-runner-label into main 2026-08-02 01:38:49 +02:00
Member

The check job compiles and links Rust natively on the runner, but requested RUNS_ON_OPENSUSE_BASE_LATEST, whose image ships cargo and rustc with no C toolchain. Any crate with a build script, plus the host-target cargo build --all-targets and cargo test --lib steps, has to link an executable, so a cold-cache run fails with error: linker `cc` not found. A warm Swatinem/rust-cache hides it, which is why it only surfaces on the first cold run.

Switch that job to RUNS_ON_OPENSUSE_DEV_LATEST (the image carrying cc/gcc/ld plus glibc and OpenSSL headers) and record the reason inline. The other two workflows stay on the base label and now say why: build-oci-image.yml compiles inside docker buildx and otherwise only runs git, nu and docker; create-release.yml only runs git and nu.

#LINKS-29

The check job compiles and links Rust natively on the runner, but requested `RUNS_ON_OPENSUSE_BASE_LATEST`, whose image ships cargo and rustc with no C toolchain. Any crate with a build script, plus the host-target `cargo build --all-targets` and `cargo test --lib` steps, has to link an executable, so a cold-cache run fails with ``error: linker `cc` not found``. A warm Swatinem/rust-cache hides it, which is why it only surfaces on the first cold run. Switch that job to `RUNS_ON_OPENSUSE_DEV_LATEST` (the image carrying cc/gcc/ld plus glibc and OpenSSL headers) and record the reason inline. The other two workflows stay on the base label and now say why: build-oci-image.yml compiles inside `docker buildx` and otherwise only runs git, nu and docker; create-release.yml only runs git and nu. #LINKS-29
ci: run Check on the dev runner label
All checks were successful
Check / clippy + fmt + tests (pull_request) Successful in 1m1s
Create release / Create release from merged PR (pull_request) Has been skipped
95790ec525
The check job compiles and links Rust natively on the runner, but requested `RUNS_ON_OPENSUSE_BASE_LATEST`, whose image ships cargo and rustc with no C toolchain. Any crate with a build script, plus the host-target `cargo build --all-targets` and `cargo test --lib` steps, has to link an executable, so a cold-cache run fails with ``error: linker `cc` not found``. A warm Swatinem/rust-cache hides it, which is why it only surfaces on the first cold run.

Switch that job to `RUNS_ON_OPENSUSE_DEV_LATEST` (the image carrying cc/gcc/ld plus glibc and OpenSSL headers) and record the reason inline. The other two workflows stay on the base label and now say why: build-oci-image.yml compiles inside `docker buildx` and otherwise only runs git, nu and docker; create-release.yml only runs git and nu.

#LINKS-29
Claude-Run deleted branch ci/LINKS-29-check-dev-runner-label 2026-08-02 01:38:49 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
a8n-tools/rusty-links!63
No description provided.