Keep the Playwright install off the broken third-party repos - #55
Merged
Conversation
Same cause as the video gate: `playwright install --with-deps` shells out to apt, apt refreshes every repository baked into the hosted runner image, and packages.microsoft.com is answering 403 today. On main this step sat for seven minutes with no output, which stops the deploys that fire on CI's completion. The browser needs its own Ubuntu dependencies and nothing from those lists, so they are removed first, exactly as the demo-video job now does.
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.
Same root cause as #54, one job over.
npx playwright install --with-depsshells out to apt, apt refreshes every repository baked into the hosted runner image, andpackages.microsoft.comis answering 403 Forbidden today.On
main(run 30832770288) that step sat for seven minutes with no output, which matters beyond one job: the Cloud Run and Firebase Hosting deploys both fire on CI's completion, so a stall here silently stops both.The browser needs its own Ubuntu dependencies and nothing from those lists, so they are removed first, exactly as the
demo-videojob now does.