setup-llvm: try ubuntu archive before apt-llvm.org on flavor=system.#74
Merged
vgvassilev merged 1 commit intoMay 13, 2026
Conversation
The Linux system path went straight to apt-llvm.org, whose codename coverage tracks recent majors only -- noble starts at llvm-17, jammy starts at llvm-14. Consumer matrices with older majors on those codenames hit `does not have a Release file` even though the ubuntu archive itself carries the package (jammy ships llvm-11..14 directly, noble ships llvm-14..16). Probe `apt-cache show llvm-N-dev` first; install from the archive when present, fall back to apt-llvm.org otherwise. This matches the install ladder consumers had inline before adopting this action (clad's pre-migration ci.yml is the reference). The verify-side smoke matrixes the existing test over `version: ['20', '14']` -- 20 forces apt-llvm.org, 14 stays in the noble archive -- so each branch is exercised on every PR.
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.
The Linux system path went straight to apt-llvm.org, whose codename coverage tracks recent majors only -- noble starts at llvm-17, jammy starts at llvm-14. Consumer matrices with older majors on those codenames hit
does not have a Release fileeven though the ubuntu archive itself carries the package (jammy ships llvm-11..14 directly, noble ships llvm-14..16).Probe
apt-cache show llvm-N-devfirst; install from the archive when present, fall back to apt-llvm.org otherwise. This matches the install ladder consumers had inline before adopting this action (clad's pre-migration ci.yml is the reference). The verify-side smoke matrixes the existing test overversion: ['20', '14']-- 20 forces apt-llvm.org, 14 stays in the noble archive -- so each branch is exercised on every PR.