CI: run Linux builds on self-hosted runners - #240
Merged
Conversation
jcelerier
force-pushed
the
ci/self-hosted-linux-jobs
branch
from
August 5, 2026 15:22
9434821 to
f8ce14d
Compare
jcelerier
force-pushed
the
ci/self-hosted-linux-jobs
branch
4 times, most recently
from
August 6, 2026 02:20
0ea3f10 to
ca70c36
Compare
jcelerier
force-pushed
the
ci/self-hosted-linux-jobs
branch
from
August 6, 2026 02:21
ca70c36 to
47eb3e5
Compare
runs-on took the matrix value as an expression, and the self-hosted entries were changed to an ARRAY. GitHub does not accept runs-on from an expression that resolves to an array, so it rejected the whole file: the run produced ZERO jobs and the PR kept displaying its older passing checks, which is why this looked queued rather than broken. The label is a plain string again. Two more from the same change: - FreeBSD was pointed at the self-hosted fleet inside a container. It uses vmactions/freebsd-vm, which needs KVM and cannot work there. Back on ubuntu-latest. - The Debian job got a second 'container:' key while it already declared 'container: image: debian:...'. A duplicate mapping key -- parsers keep the last one silently, which is how it survived review.
The self-hosted runners inject a compiler cache launcher that exists only in the images the fleet mirrors, and debian:testing is not one of them -- the job got the stock image, every compile failed on the missing launcher, and CMake reported that the C compiler itself was broken. trixie was already in the matrix, so testing is dropped rather than repointed, along with its now-dead exclude. debian:testing is a rolling target that has moved past trixie, so mirroring it would mean rebuilding that image forever to track whatever testing happens to be.
trixie is no longer testing -- it released as Debian 13 and is now stable, so the earlier change lost testing coverage rather than keeping it. Debian's own Release files say it plainly today: stable=trixie (13.6), testing=forky. Pinned to the codename rather than the `testing` tag. `debian:testing` is a moving target the CI image mirror cannot follow without rebuilding forever to track whatever testing happens to be; a codename is a stable thing to mirror, and repointing it when testing rolls over is a one-line change. The image was built and pushed BEFORE this commit, so the tag resolves to an image that carries the compiler-cache launcher -- which is what the earlier debian:testing leg was missing.
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
1 participant
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.
Run the Linux x86_64 jobs on self-hosted runners.