ci: run Check on the dev runner label #141
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/YT-86-check-dev-runner-label"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The check job compiled Rust natively on RUNS_ON_OPENSUSE_BASE_LATEST, whose image has no C toolchain, so it carried an "Ensure a C toolchain" step that probed for zypper / apt-get / apk / dnf and installed gcc on every run. The runner labels already split by what a job does: RUNS_ON_OPENSUSE_DEV_LATEST is the image that ships cc / gcc / ld plus the glibc and OpenSSL headers ring and libsqlite3-sys need. Request that label and delete the install step rather than re-solving the image's job on every run.
Every runs-on in .forgejo/workflows/ now carries a comment justifying its label: check.yml compiles on the runner (dev), build-linux.yml and build-windows.yml compile inside docker buildx (base), create-release.yml only runs git and one HTTP call (base), and build-macos.yml sits outside the OpenSUSE split on RUNS_ON_MACOS with its Xcode probe.
crates/yt-cli/tests/ci_runner_labels.rs enforces all three properties mechanically, so the fallback cannot come back unnoticed.
#YT-86