-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: disable incremental compilation in dogfood to reduce target dir size #4513
Conversation
I tried this, and it appeared to slow down the inevitable "no space left on device", though not overcoming it. The |
Interestingly, if I run Perhaps a way to clear the incremental caches between dogfood and dogfood_tests would give us sufficient wins without losing all of the benefits of incremental compilation. |
Hmm, I think the tests currently run in parallel, so we'd have to run them in linear order which will probably worsen execution time. |
Clippy seems to invoke rustc with EDIT: nevermind it seems to work, pebkac. |
reduces target/ dir size of when "cago test"ing by around 2 gigs.
…r size even further.
11d256a
to
a1ecf39
Compare
previous behaviour: cargo build with this branch: cargo build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good to me. Just deleted a 50GB target directory from Clippy yesterday.
@bors r+ |
📌 Commit a1ecf39 has been approved by |
tests: disable incremental compilation in dogfood to reduce target dir size tests: execute dogfood tests with incremental compilation disabled reduces target/ dir size of when "cargo test"ing by around 2 gigs. changelog: none
☀️ Test successful - checks-travis, status-appveyor |
Thanks, @matthiaskrgr! |
tests: execute dogfood tests with incremental compilation disabled reduces target/ dir size of when "cargo test"ing by around 2 gigs.
changelog: none