馃懛 ci: refresh only the apt list the frontend job writes - #2260
Merged
Conversation
The frontend job installs clang from apt.llvm.org, and `apt-get update` reads every list on the runner image rather than the one the step just added. On 2026-09-09 Google's Chrome repository served a Packages.gz whose hash did not match its Release file, so the command exited 100 and clang was never installed. apt.llvm.org was healthy throughout and its index fetched cleanly; a third party we do not depend on decided whether the job ran. Pointing the refresh at the LLVM list alone removes that dependency and skips eleven megabytes of indexes the job has no use for. Keeping List-Cleanup off preserves the image's existing lists, so lcov still resolves from the Ubuntu archive without a second refresh.
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
frontendjob stopped installing clang, which tookci-gatedown with it onmainand on every open pull request. 馃敡 The step addsapt.llvm.orgto the runner's sources and then runs a bareapt-get update, which refreshes every list on the image rather than the one it just wrote. On 2026-09-09 Google's Chrome repository served aPackages.gzwhose hash did not match itsReleasefile,apt-getexited 100, and the job ended beforeapt-get installran. Run 34384212771 failed that way twice, once on its own and once on a rerun of the failed jobs, so the cause was not a passing network hiccup. The LLVM index fetched cleanly in both attempts, and thellvm-toolchain-noble-22suite still publishesclang-22: a third party the build has no dependency on decided whether the build ran.Pointing the refresh at
sources.list.d/llvm.listthroughDir::Etc::sourcelist, withDir::Etc::sourcepartsemptied, restricts the command to the repository the step controls.APT::Get::List-Cleanup=0leaves the image's existing lists in place, solcovstill resolves from the Ubuntu archive without a second refresh. The narrower fetch also skips roughly eleven megabytes of indexes the job never reads.Any repository on the runner image can break again the same way. This change limits the blast radius to the one repository the step installs from, so an unrelated publisher shipping a bad index no longer fails the build.
Closes #2259