We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem cargo clean puts a lock on the package cache (cargo home) but I think it should not need it at all?
cargo clean
Steps
cargo fetch
Blocking waiting for file lock on package cache
Possible Solution(s) I don't really see why we need to take the $CARGO_HOME lock into account here, after all we only need to rm -rf target..?
$CARGO_HOME
rm -rf target
Notes
Output of cargo version: cargo 1.40.0-nightly (8b0561d68 2019-09-30)
cargo version
cargo 1.40.0-nightly (8b0561d68 2019-09-30)
The text was updated successfully, but these errors were encountered:
I think it would be fine to move this line below line 63 if you want to fix this.
Sorry, something went wrong.
Thanks!
Auto merge of #7502 - matthiaskrgr:dont_lock_target_dir_7490, r=ehuss
d5d7557
don't lock the package cache when cleaning target dir. Fixes #7490
9883d20
Successfully merging a pull request may close this issue.
Problem
cargo clean
puts a lock on the package cache (cargo home) but I think it should not need it at all?Steps
cargo fetch
of some git repo run on project 1.cargo clean
a different repo at the same time=>
Blocking waiting for file lock on package cache
Possible Solution(s)
I don't really see why we need to take the
$CARGO_HOME
lock into account here, after all we only need torm -rf target
..?Notes
Output of
cargo version
:cargo 1.40.0-nightly (8b0561d68 2019-09-30)
The text was updated successfully, but these errors were encountered: