Repository navigation
fix(ci): bound GoReleaser build concurrency on self-hosted runners - #323
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
GoReleaser's six cross-platform builds exhausted memory on the 8-vCPU / 16-GiB self-hosted runners. Host logs show the OOM killer terminating a Go
compileprocess and the runner exiting; #320 also lost its runner during the snapshot build, with memory-pressure messages on that host.Limit both the Extended CI snapshot build and the release artifact build to one GoReleaser task, two parallel Go package builds (
GOFLAGS=-p=2), andGOMAXPROCS=2per Go process. All six platform targets, checks, cache isolation, release permissions, and publication approval remain in place. This bounds concurrency; it is not a hard memory cap.Validation:
make fmt verify test buildpassed, including race-enabled Go tests and plugin/Skill regressions.goreleaser checkwith the pinned v2.17.0 passed.0e3fc0591088b4d6f62dcc197400467e5a5fa1aa.--parallelism=1,GOFLAGS=-p=2,GOMAXPROCS=2, all six target builds, archives, and checksums; all Linux runners remained online after completion.Related infrastructure failures: #315, #320. Their feature changes are not included in this PR.