-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Rust crashes due to unknown cache changes #89457
Comments
I just realized this asked for RUST_BACKTRACE=full and I provided RUST_BACKTRACE=1 (as I was already using that on my tests), sorry. If there's a command I can use to revert my Rust install in a way that won't trigger a rebuild when I try it against my preserved faulty cache (which I'd have to move back to its original position, of course), I'm more than willing to run it and provide the proper backtrace. |
The top of the stack trace seems identical to #89260 |
I'm still seeing an ICE with a very similar backtrace. It happens when building https://github.com/ZcashFoundation/zebra , but only when the on-disk cache is in a particular state. (Approximately every ~100 builds.) So I can't provide an easy reproduction. I'm using:
Backtrace
|
Closing assuming the previous "it's a duplicate" is correct, because it seems so to my eyes. Should be fixed by either that or #93064 |
Meta
Version:
Error output
Backtrace
Encountered while working on a project of mine. I copied the directory to another location to back it up, and went there to confirm the same command exhibited the same behavior. The changed path triggered a rebuild and this caused rustc to work without issue, leading me to believe there's a malformed cache. I have been updating my Cargo.toml, from additions to removals to even a version upgrade. That said, my only change before my last successful compile and this one was introducing a few errors while I expanded functionality. I was hoping my malformed code would offer a MRE, yet unfortunately (or fortunately) Rust can handle it.
I am on nightly and went to the latest nightly to check this was still an issue. Doing so rebuilt my cache yet again, hence why my version info is what it is (it's rustup's logs on what it upgraded from). I do have a copy of the cache directory, as it caused errors, I'd be willing to send privately if it'd be beneficial. I never directly edited it. As for the code edits, those would be harder to track down due to the fact I'm in the middle of a commit, and can't confirm what my code was on the last successful compile in order to provide such a diff.
The text was updated successfully, but these errors were encountered: