ci(dx-e2e): cap matrix parallelism to avoid tx3up install saturation#28
Merged
Conversation
A manifest change invalidates that channel's cache key, so every matrix cell cache-misses and runs `tx3up install` simultaneously. The burst of `releases/latest` lookups trips a GitHub API secondary rate limit, which tx3up surfaces as "No manifest asset found in latest release" — scattered install failures unrelated to the journeys (seen on both the beta and stable promotion merges). Set `max-parallel: 3` on both channel jobs so at most three cells install at once. A single-channel cache-miss burst drops from 9–12 concurrent installs to 3, comfortably under the limit. Warm-cache runs are unaffected in substance and only marginally slower (journeys are seconds-scale). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
scarmuega
force-pushed
the
ci/dx-e2e-cap-install-parallelism
branch
from
4e9aa2f to
4f930a1
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
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.
Problem
A manifest change invalidates that channel's cache key (
hashFiles(manifest-<channel>.json)in the composite action), so every matrix cell for that channel cache-misses and runstx3up installat the same time. The burst ofreleases/latestlookups trips a GitHub API secondary rate limit, which tx3up surfaces as:These are scattered, install-step failures unrelated to the journeys. Observed on both recent manifest merges (#26 beta, #27 stable); each needed a manual re-run to go green.
Fix
Set
max-parallel: 3on both channel jobs. A single-channel cache-miss burst drops from 9–12 concurrent installs to 3, comfortably under the rate limit. Warm-cache runs (the common case) are unaffected in substance and only marginally slower — the journeys are seconds-scale.max-parallelis per matrix job, sostableandbetakeep their own caps; since a manifest edit only cache-misses one channel, the effective worst-case burst is 3.Notes
05-invokestays intentionally red on beta.🤖 Generated with Claude Code