-
Notifications
You must be signed in to change notification settings - Fork 13.3k
thread 'rustc' panicked at 'called Option::unwrap()
on a None
value
#92195
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
Comments
I don't know what I did, but I can't reproduce it anymore. I started deleting and rebuilding until rustc didn't panice anymore. And now the unchanged repro can be built successfully too. I guess the bug originated in the files rustc creates during builds for chaching or whatever and the repro wouldn't have worked on other machines anyway. |
I was about to raise the same issue. Seems to be an issue with incremental build.
|
This should be fixed on the latest nightly. |
Since I can't replicate it anymore, I can't verify it. |
Just hit this issue on stable with |
I have ran into a similar issue, but that also seems to be related to incremental compilation and is on latest nightly: #92221. |
@rustbot label +A-incr-comp |
On latest nightly:
cc @Aaron1011 |
Oh you're right. I added my comment over there. Thanks |
Closing as a probable duplicate of #91696 |
Code
Only can provide an unminified repro right now, located in this repo (branchrustc-bug-repro
)If you check out the previous commit the build will go through without any compiler errors or rustc panics:So it must be something that happend in this commit, but I can't say what exactly yet.Meta
rustc --version --verbose
:Error output
RUST_BACKTRACE='full'
The text was updated successfully, but these errors were encountered: