-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
cargo check panic at 'failed to lookup SourceFile
in new context' after refactor
#92595
Comments
Everything works again after running |
I wasn't able to set up a minimal example for this bug yet, but you can use my public repository to reproduce:
|
SourceFile
in new context'SourceFile
in new context' after refactor
In case it's helpful: I also hit this only once on v0.0.212-9018-g917890bab of rust-clippy, but couldn't reproduce it after |
Hi everyone, this bug in beta is so prevalent that lots of tests in https://github.com/google/autocxx/blob/main/integration-tests/tests/integration_test.rs have had to be disabled for beta builds. Incremental compiles fail crazily often, and it is breaking the integration tests that use beta channel on the CI, always with this same compile panic. If the beta channel gets promoted to stable in this state, it will look like a major compilation regression for many |
@philipcraig You should probably open a new issue for this, I just tested this scenario again and it seems to compile without errors now. I'll probably close this issue soon |
Closing as I believe this is now resolved. |
This error occurred when running
cargo check
after refactoring a module folder to a module file.Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: