Repository navigation
ci(release): limit GoReleaser build parallelism - #304
Merged
Merged
Conversation
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.
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
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.
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 2halves that. The out-of-memory kill itself is inferred from these numbers, not observed on the runner; the next release run is the test.