Repository navigation
chore: stop building debug info by default - #9
Merged
Merged
Conversation
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.
Why
Dev and test builds do not read DWARF, and it multiplies what every target directory and the shared build cache hold. Measured on this machine: the local
kachestore holds 335 GiB, of which 320 GiB isdev-profile artifacts, with individual crates above 1 GiB (astrided_kerneldev rlib is 1.13 GiB). None of that is read bycargo test.What
[profile.release] debug = truebecomes0, and dev and test getdebug = 0as well. A benchmark run that wants symbols can ask for them withCARGO_PROFILE_RELEASE_DEBUG=truerather than paying for them in every build.Note
CARGO_PROFILE_DEV_DEBUG=2(orline-tables-onlyfor backtraces alone) restores debug info for a session without changing this file.