fix(ci): back off OCM release asset retries#102996
Merged
Merged
Conversation
Contributor
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: fix(ci): back off OCM release asset retries This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
Contributor
Author
|
Land-ready at exact head Proof:
The change is release-workflow-only and preserves the existing fail-closed checksum gate. Post-land performance proof will run at the final release SHA. |
Contributor
Author
|
Merged via squash.
|
Simon-XYDT
pushed a commit
to Simon-XYDT/openclaw
that referenced
this pull request
Jul 9, 2026
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 10, 2026
RomneyDa
pushed a commit
that referenced
this pull request
Jul 13, 2026
(cherry picked from commit 372b527)
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.
What Problem This Solves
Fixes an issue where release performance validation could fail before exercising OpenClaw because the pinned OCM release asset returned a transient HTTP 504. The workflow retried only three times at fixed one-second intervals, so every attempt could hit the same unhealthy CDN/egress window.
This happened twice in performance run 29032864140: each attempt received four 504 responses and produced no Kova metrics or artifacts. A third attempt later downloaded the same asset successfully, and concurrent Blacksmith runners also split between success and 504 for the identical URL.
Why This Change Was Made
The checksum-pinned, idempotent download now gets eight retries over a bounded 180-second retry window, uses curl's default backoff instead of a fixed one-second retry storm, and retries all transport errors including refused connections. The existing SHA-256 verification remains mandatory before extraction.
No mirrors, cache-busters, unpinned versions, or alternate binaries are introduced.
User Impact
No product runtime change. Release performance checks are more resilient to short GitHub release-asset CDN or runner-egress outages without weakening supply-chain verification.
Evidence
v0.2.15, asset id410473079, size2617319, and digestsha256:b849b8de5d77e97e0df9319703254ae95e29d7f26a7552ea79bf173ff110ea0a, matching the workflow pin.git diff --checkpassed.node scripts/check-workflows.mjspassed zizmor and the repository workflow interpolation guard.autoreview --mode localreported no accepted/actionable findings (patch is correct, confidence 0.98).