Stop a third-party apt repo failing the video gate - #54
Merged
Conversation
The gate went red on main with apt exit 100, and the cause was not ffmpeg: E: Failed to fetch https://packages.microsoft.com/repos/azure-cli/... 403 E: The repository ... is no longer signed. `apt-get update` refreshes every repository baked into the hosted runner image, so an unrelated publisher answering 403 takes the whole update with it. The same lists are the likely cause of the two thirteen-minute hangs earlier today. This job needs Ubuntu's own archive and nothing else, so those lists are removed before the update runs. That matters beyond one job: the Cloud Run and Firebase Hosting deploys both fire on CI's completion, so this gate failing for a reason unrelated to this repository stops both.
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
demo-videogate went red onmain(run 30832283753), and the cause was not ffmpeg:apt-get updaterefreshes every repository baked into the hosted runner image, so an unrelated publisher having a bad day takes the whole update down with exit 100. The same lists are the likely cause of the two thirteen-minute hangs onmainearlier today, which is why the job also gained a timeout and a skip-if-already-present check in #53.This job needs Ubuntu's own archive and nothing else, so those lists are removed before the update runs.
It matters beyond one job: the Cloud Run and Firebase Hosting deploys both fire on CI's completion, so this gate failing for a reason that has nothing to do with this repository quietly stops both.