Repository navigation
Prefer existing Ubuntu mirrors for browser CI dependencies - #83
Merged
Merged
Conversation
Narrator
marked this pull request as ready for review
October 26, 2026 20:58
|
View your CI Pipeline Execution ↗ for commit e569666
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
Narrator
changed the title
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
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.
Browser CI repeatedly waits on slow Azure Ubuntu package downloads before any Domscribe test starts. Prefer the hosted runner’s existing archive.ubuntu.com and security.ubuntu.com mirrors, retaining its existing Azure URI as the final fallback. Rewrite priorities only in a prepared copy, validate the known runner list before sudo install, and preserve URI transports, metadata, signed package verification and fatal --with-deps installation. An overall five-minute browser setup limit keeps failures bounded.
Validation:
Evidence/tradeoff: scheduled main40385978344 timed out in Chromium setup; PR82 job121839308398 showed Get/Ign stalls. The first timeout-only revision failed four actual hosted five-minute installs because downloads continuously progressed slowly; that version is superseded. Upstream runner images already set15-second inactivity/retry bounds, so duplicating them cannot fix a slow-but-progressing mirror. The current revision changes mirror preference rather than ignoring errors or skipping dependency installation. A complete network outage or slow fallback can still fail; improved success rates are not claimed from one run.
APT mirror priority semantics: https://manpages.debian.org/bookworm/apt/apt-transport-mirror.1.en.html . Upstream configuration: actions/runner-images#14643 . Separate from Vite8 support PR82; local apt execution is not claimed (host lacks apt-config).