fix(ci): retry sqlite3mc-wasm download on transient DNS/TLS failures#23333
Merged
spalladino merged 1 commit intoMay 16, 2026
Merged
Conversation
Collaborator
Author
Flakey Tests🤖 says: This CI run detected 2 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
spalladino
approved these changes
May 16, 2026
This was referenced May 16, 2026
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.
Motivation
The merge-train/spartan train PR (#23253) was dequeued from the merge queue this morning because grind run
x9failed duringcompile_all:CI logs:
The branch CI on the same commit (run 25958983932) passed — only one of the 10 grind shards hit the DNS flake, but the merge-queue fail-fast tore the whole run down. The other 9 grinds and the ARM run were still pending when the queue dropped #23253.
Approach
Add curl retry flags to
yarn-project/sqlite3mc-wasm/scripts/vendor.shso a one-offCould not resolve host(or any other transient curl failure) doesn't fail the build.--retry 5 --retry-delay 2 --retry-all-errors --retry-connrefusedgives ~10s of total backoff, which is plenty for a momentary DNS hiccup but bounded for genuine outages.This is the only curl in the yarn-project build path that hits GitHub release assets, so this is a targeted fix rather than a sweep.
Verification
./bootstrap.sh cirequires EC2 spawn and isn't runnable from inside the container. Locally verified thatvendor.sh ensurestill downloads and validates the pinned artifact correctly.ClaudeBox log: https://claudebox.work/s/89dacb14037285cd?run=1