Cap GoReleaser build parallelism to avoid OOM on the release runner#466
Merged
Conversation
The first GoReleaser run of the new release pipeline was killed on the CI runner. The `Run GoReleaser` log stops dead at `building binaries` with four concurrent builds in flight and no error or `##[error]` annotation, even in the raw downloaded log -- the signature of the runner agent being OOM-killed. A single cold `go build` of this project peaks at ~5.6 GB RSS. GoReleaser defaults `--parallelism` to the CPU count (4 on ubuntu-latest), so building four targets at once needs ~22 GB on a 16 GB runner and the runner thrashes into swap before dying. Pass `--parallelism 1` so the targets build one at a time and memory stays bounded. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
The first GoReleaser run of the new release pipeline (run 26036447466) failed. The
Run GoReleaserlog stops dead atbuilding binarieswith four concurrent builds in flight, then the job is finalized asfailure~8.5 minutes later with no error message and no##[error]annotation — even in the raw downloaded log. That signature means the runner agent itself was OOM-killed.Cause
A single cold
go buildof this project peaks at ~5.6 GB RSS:GoReleaser defaults
--parallelismto the CPU count (4 onubuntu-latest), so building four targets at once needs ~22 GB on a 16 GB runner. The runner thrashed into swap (hence 8.5 min for sub-minute builds) and was killed. The Dockerimagejob succeeded because it only builds the two linux targets via buildx.Fix
Pass
--parallelism 1so targets build one at a time and memory stays bounded (~6 targets × ~45 s ≈ 5 min).🤖 Generated with Claude Code