Skip to content

ci(release): limit GoReleaser build parallelism - #304

Merged
ernado merged 1 commit into
mainfrom
ci/release-parallelism
Nov 16, 2026
Merged

ernado merged 1 commit into
mainfrom
ci/release-parallelism

Conversation

@ernado

@ernado ernado commented Nov 16, 2026

Copy link
Copy Markdown
Member

The v0.12.0 release run died twice at the same point, while building four targets at once: The runner has received a shutdown signal. Nothing was published.

Measured locally with a cold build cache, one target (linux/arm64): peak compiler RSS is 4.8 GB at v0.12.0 (gotd/td v0.165.0) against 4.4 GB at v0.11.0. GoReleaser builds one target per CPU, so four at once need about 19 GB on a 16 GB runner.

--parallelism 2 halves that. The out-of-memory kill itself is inferred from these numbers, not observed on the runner; the next release run is the test.

The v0.12.0 release run was killed twice while building four targets
at once ("The runner has received a shutdown signal"). One target
peaks at about 4.8 GB of compiler memory with gotd/td v0.165.0, so four
in parallel exceed the 16 GB hosted runner.
@ernado
ernado merged commit ae72ae8 into main Nov 16, 2026
4 checks passed
@ernado
ernado deleted the ci/release-parallelism branch November 16, 2026 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant