build: debug info off by default for dev and test builds - #282
Merged
Conversation
Measured across this fleet on 2026-08-22: 22 GB / ~40 min with debug info vs 4.4 GB / ~10 min without, on the same tree. That was being carried as five `CARGO_PROFILE_*` environment variables every session had to know and remember, so a fresh clone, a CI runner, or a session that forgot all got the expensive build. `[profile.test]` inherits from `dev`, so this one entry covers `cargo build` and `cargo test` alike. lance-graph set the same default in its own manifest (#962); MedCare-rs followed today; this closes the same gap here. Verified it reaches the compiler rather than trusting manifest semantics: with no `CARGO_PROFILE_*` variables set, the rustc invocation carries `-C strip=debuginfo` and no `-C debuginfo=2`. Given up: line numbers in panic backtraces. `debug = "line-tables-only"` restores them at a fraction of full debug info when a debugging session needs them — a deliberate temporary edit, not a reason to keep the default expensive.
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_cc08cfcf-91fd-4f92-b71d-1c7414b51bac) |
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.
Measured across this fleet on 2026-08-22: 22 GB / ~40 min with debug info vs 4.4 GB / ~10 min without, on the same tree.
That was being carried as five
CARGO_PROFILE_*environment variables every session had to know and remember — so a fresh clone, a CI runner, or a session that forgot all got the expensive build. A default belongs in the manifest, not in each session's environment.[profile.test]inherits fromdev, so this one entry coverscargo buildandcargo testalike. lance-graph set the same default in its own manifest (#962); MedCare-rs and OGAR followed today.Verified it reaches the compiler rather than trusting manifest semantics: with no
CARGO_PROFILE_*variables set, the rustc invocation forndarraycarries-C strip=debuginfoand no-C debuginfo=2.Given up: line numbers in panic backtraces.
debug = "line-tables-only"restores them at a fraction of full debug info when a debugging session needs them — a deliberate temporary edit, not a reason to keep the default expensive.Note: this repo's
rust-toolchain.tomlpins1.95.0, deliberately different from the 1.97.1 the rest of the fleet uses. Untouched.Generated by Claude Code