-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Interrupting cargo can cause linker errors #8838
Comments
I just cleaned the build artifacts and it works now, so it's related to incremental somehow. |
This was intended to be fixed with #8087, but it appears that something else is still leaking through. Without a reliable reproduction, however, it unfortunately may be somewhat difficult to dig into why this issue is getting past that PR. |
I just ran into this, fwiw - happy to provide any information that might help track it down but obviously as you said it's tough to really identify the root cause |
and of course, sccache is making this persist through a cargo clean. |
Ran into this again:
|
I'm unsure but think I've run into the same issue.
This occurred when used in conjunction with cargo watch, which I'm guessing interrupted the build when there was a filesystem change. |
@bjorn3 says
So this may be a duplicate of rust-lang/rust#81280. |
Problem
I interrupted cargo while running a build. Now, all builds fail:
Steps
I can't reproduce this reliably. I was running
RUST_BACKTRACE=1 xpy test src/test/rustdoc --test-args rustdoc/unit-return.rs
after modifying compiletest, so it was building compiletest itself. I hit ctrl+c a couple different times to make changes.Possible Solution(s)
Notes
Output of
cargo version
:cargo 1.48.0-beta (65cbdd2 2020-10-14)
The text was updated successfully, but these errors were encountered: