ci: strip full debuginfo from test profile to fix linker OOM#828
Merged
vieiralucas merged 1 commit intomainfrom Apr 28, 2026
Merged
ci: strip full debuginfo from test profile to fix linker OOM#828vieiralucas merged 1 commit intomainfrom
vieiralucas merged 1 commit intomainfrom
Conversation
Add `[profile.test] debug = "line-tables-only"` to the workspace manifest. Default test-profile DWARF was spiking `ld` past the GitHub runner's ~7 GB free RAM during `cargo nextest run` on large E2E test binaries, killing it with `signal 7 [Bus error]`. line-tables-only keeps file:line backtraces but drops type/variable DWARF, cutting the linker's working set enough to land on the default runner. No effect on dev/release profiles.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
4 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Summary
Stabilize CI runner flakes (2/3) — fix
cargo nextest runlinker OOM.Default
[profile.test]emits full DWARF, which on the workspace's E2E test binaries spikedldpast the default GitHub runner's ~7 GB free RAM and killed it with `collect2: fatal error: ld terminated with signal 7 [Bus error], core dumped`. Pattern hit E2E lambda-runtime + lambda-container-clis partitions repeatedly across PRs #823, #824, #826.Fix: set `[profile.test] debug = "line-tables-only"` in the workspace `Cargo.toml`. line-tables-only keeps file:line in backtraces (so panics still point at source lines) but drops per-symbol type and variable DWARF, which is what blows up linker memory. No effect on `dev`/`release`.
Verified locally: `cargo check --workspace --tests` succeeds.
Sibling PRs: #827 (nextest retries + disk diagnostics) and a follow-up for ECS task failure diagnostics.
Test plan
Summary by cubic
Fix CI linker OOM by setting
[profile.test] debug = "line-tables-only"in the workspaceCargo.toml. Backtraces still show file:line,cargo nextest runno longer exhausts RAM on the default GitHub runner, anddev/releaseare unchanged.Written for commit df66de6. Summary will update on new commits. Review in cubic