fix(ci): make aztec-up verdaccio prime retry patiently#23983
Draft
AztecBot wants to merge 1 commit into
Draft
Conversation
The aztec-up test primes a local verdaccio registry by running 'npm i -g @aztec/aztec ...', which resolves every transitive dependency fresh from npmjs. A transient upstream/registry miss can 404 a single uncached version even when it is published (observed on merge-train CI: @aws-sdk/credential-provider-env@^3.972.46 404'd although it had been published ~13h earlier). The default retry (3 attempts, 5s apart) is too impatient to ride out the blip and dequeued the spartan-v5 merge train. Retry the prime up to 8 times with 30s backoff before failing.
AztecBot
added
ci-draft
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.
Why
The
merge-train/spartan-v5train PR (#23975) was dequeued from the merge queue. The merge-queue-heavy CI failed in grind runx8-full(ci log) at theaztec-uptask (log):The
aztec-uptest primes a local verdaccio registry by runningnpm i -g @aztec/aztec ..., which resolves every transitive dependency fresh from npmjs (proxied through verdaccio). The 404'd version@aws-sdk/credential-provider-env@3.972.46was actually published ~13h before the run, so this was a transient verdaccio↔upstream-npm fetch miss, not a missing package — and unrelated to the three commits in the train (#23967, #23821, #23976). The aws-sdk dependency tree resolves cleanly again now.The default
retryhelper (3 attempts, 5s apart) only covered ~2 min, which wasn't enough to ride out the blip, so the prime failed and the train was dequeued.What
Retry the verdaccio prime up to 8 times with 30s backoff before failing. The happy path is unchanged (first attempt breaks immediately); only failures pay the extra patience.
This is CI resilience hardening, not a code fix in the train. The same change should be ported to
next(the non-v5aztec-up/bootstrap.shis identical).Created by claudebox · group:
slackbot