Develop#400
Merged
cristibleotiu merged 4 commits intomainfrom May 6, 2026
Merged
Conversation
…t build cost Collapse the three previous workflows (build_testnet, build_mainnet, build_gpu) into one workflow per branch: - build_develop.yml: devnet CPU -> testnet CPU -> devnet GPU -> testnet GPU - build_main.yml: mainnet CPU -> mainnet GPU (with version git tag) Steps run sequentially in a single job (one runner, one buildx-cloud session, one Docker login), and a shared concurrency group prevents a develop build and a main build from overlapping. Build steps use `if: !cancelled()` so a failure in one image does not block subsequent images, since the images are independent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The cloud builder's gcPolicy caps cache at 25GiB. After 2 CPU builds the cache fills with non-GPU layers, then the GPU base (libtorch + CUDA) cannot be extracted and the GPU build fails with "no space left on device" inside /buildkit/data/runc-overlayfs/snapshots/. Prune the builder cache right before the GPU pair so the CPU layers (which the GPU builds cannot reuse anyway) are evicted. The two GPU builds still share the freshly cached GPU base, so we keep within-pair cache reuse. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Each image (devnet/testnet CPU+GPU on develop, mainnet CPU+GPU on main) is now its own job, chained via `needs:` to keep them sequential. The run-summary view shows one box per image instead of a single job with nested steps, and individual builds can be re-run on their own. Buildx-cloud cache stays shared across jobs because it lives on the cloud builder (server-side), so layer reuse between adjacent builds is preserved. The CPU-to-GPU prune still runs at the start of the first GPU job to free the CPU layers from the cache cap. Failure semantics unchanged: `if: !cancelled()` on downstream jobs lets each build run independently of the previous one's outcome. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
toderian
approved these changes
May 6, 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
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.
No description provided.