-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Fixed incorrect locking logic when artifact-dir == build-dir #16385
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
Conversation
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.
Thanks!
|
Let me know if you're willing to do a beta-backport, @ranger-ross. No worries if you are busy. For cherry-picking, it would need this PR, as well as #16380 to make CI happy, and should be filed against the branch https://github.com/rust-lang/cargo/tree/rust-1.93.0. (See doc) |
|
sure I can take a crack at it :) |
|
The same flakiness on aarch64-pc-windows-msvc (again) requeuing |
### What does this PR try to resolve? This PR backports #16385 along with some test fixes from #16380 to make CI happy. ### How to test and review this PR? r? @weihanglo
What does this PR try to resolve?
This PR fixes incorrect locking behavior in
layout.rsthat forgets to lock thebuild-dirwhenbuild-dir == artifact-dir.This is problematic is the default for both are
$WORKSPACE/targetand I overlooked this :(Issue reported in #16384
How to test and review this PR?
See the tests. You can also run
cargo checkand check for the presence of.cargo-lockr? @weihanglo