Repository navigation
Give the optimized native build 4 GiB; show its log on failure - #586
Merged
Merged
Conversation
The server crate's release compile now peaks near 2.3 GiB, so the 2 GiB limit intermittently OOM-killed rustc (exit 101) and hid why. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rmcdaniel
enabled auto-merge
October 21, 2026 11:11
12 tasks
|
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.
Part of #325.
published-sdk-adaptersbuilds one optimized native binary for the deadline-health cells in a container limited to 1 CPU and 2 GiB. That build has been failing intermittently with exit 101 after 3.5–5 minutes on #562, #575, #578 and #581, while successful builds take 5–9 minutes.Cause
rustc is OOM-killed. Rebuilding #562's head locally with the same script, image and limits fails with
(signal: 9, SIGKILL: kill)while compiling the server crate. With a 4 GiB limit the same build succeeds, with sampled peak memory of 2.31 GiB. The crate now sits above 2 GiB. Earlier refactors that shrank generic code only moved individual PRs back under the line. The test-build jobs in this workflow already moved to 4 GiB for the same reason.Change
build.jsonrecords the new limit.exit code 101.The binary is the same; only the compiler's memory allowance changes.
🤖 Generated with Claude Code