release: the mirror step's cap was shorter than the deadline it was guarding - #509
Merged
Sunrisepeak merged 1 commit intoAug 25, 2026
Merged
Conversation
…uarding
`mirror_res.sh` gives GitCode `MIRROR_LEG_DEADLINE_GTC=2400s` because that
host shapes inbound traffic. The step around it killed the script at 600s,
so that budget could never be spent — of two disagreeing limits the shorter
always wins, and every release ended the same way:
The action 'Mirror binaries to xlings-res/mcpp (gh + gtc)'
has timed out after 10 minutes
with GitHub's eight assets uploaded in seconds and GitCode's three large
ones cut off, only the small `.sha256` files through. v2026.8.25.1 and
v2026.8.25.2 both, measured; both were finished by hand with `gtc` and
verified byte-for-byte.
The comment on that value described a design that no longer exists — a
per-asset `MIRROR_UPLOAD_TIMEOUT` of 180s. The script's own comment records
why it went ("the old per-asset cap failed four releases in a row"), but
this number, calibrated to it, stayed behind.
45 > 40 leaves the script room to reach its own deadline and report what it
abandoned by name, which is what the value exists for; the job's
`timeout-minutes: 30` is the outer backstop.
Also moves the workspace bootstrap pin to 2026.8.25.2. It named
2026.8.17.1, which the index no longer offers, so building mcpp from a
fresh clone tried to install a version that is not there — the
cross-validation channel had to `rm -f .xlings.json` to get past it.
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
2 participants
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.
Two limits disagreed and the shorter always won.
mirror_res.shgives GitCode 2400s (it shapes inbound traffic); the step killed it at 600s. Every release since has ended withtimed out after 10 minutes, GitHub's eight assets through in seconds and GitCode's three large ones cut off — v2026.8.25.1 and v2026.8.25.2 both, each finished by hand withgtcand verified byte-for-byte.The comment on that value described a per-asset cap the script no longer has; its own comment records that the per-asset design "failed four releases in a row" and was replaced by per-leg deadlines. The number stayed.
Also bumps the workspace bootstrap pin to 2026.8.25.2 — it named 2026.8.17.1, which the index no longer offers, so a fresh clone could not build mcpp without deleting the file first.