ci: avoid azure mirrors if possible - #20
Open
espy wants to merge 1 commit into
Open
Conversation
janl
force-pushed
the
ci-use-ubuntu-mirrors
branch
from
April 14, 2026 11:25
0b311e2 to
dee6b5b
Compare
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.
Overview
Avoid the Azure Ubuntu mirrors if possible, since they can slow down CI immensely. Other project also do this, this particular PR is inspired by: servo/servo#39190
I've added this change directly in the
bin/run-test.shfile just before we install Playwright, which is where all these dependencies come from. We previously tried doing this in the GH workflow yaml, but that didn’t take, maybe this approach is better.This PR also reverts my previous attempt at speeding this process up by installing fewer dependencies for Playwright, but that turned out to not have any effect.
Testing recommendations
Trigger a CI run and compare it to a
masterrun at about the same time of day (important!).Measurements
First comparison against an unimproved branch:
Today at 10:35 AM -> 11:43 AM (old -> This PR)
47m 39s -> 14m 44s
Slowest tests:
couchdb-browser (3.1, firefox, TYPE=mapreduce ADAPTERS=http npm test)21m 19s -> 1m 35s
browser-adapter (firefox, idb, npm test)22m 35s -> 5m 21s
browser-adapter (webkit, memory, TYPE=find PLUGINS=pouchdb-find npm test)18m 28s -> 1m 21s
browser-adapter (firefox, idb, TYPE=find PLUGINS=pouchdb-find npm test)47m 8s -> 2m 7s
Checklist
docsfolder -> Not applicable