-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
ICE in src/librustc/ty/query/plumbing.rs when compiling incrementally #59716
Comments
Incremental errors typically mean, that you changed something between two build. Have you moved something? Renamed a variable, a method? Do you have by chance a backtrace? :| |
I may have made this change: @@ -2,9 +2,8 @@ use std::io::{self, *};
use std::sync::atomic::*;
fn main() {
- //std::thread::spawn(|| panic!()).join().unwrap_err();
- //println!("main after join");
- panic_in_write_doesnt_flush_in_drop();
+ std::thread::spawn(|| panic!()).join().unwrap_err();
+ println!("main after join");
}
#[test]
fn panic_in_write_doesnt_flush_in_drop() { Sorry, no backtrace. |
Same here in my private project using today's nightly:
What's peculiar is the fact that it fails on various structs - right now it failed on my Edit: the error's gone after |
I also had this bug. Happened after I ran a
I don't know exactly what rustfmt changed, but here's all the changes since my last commit (mostly doc changes): https://gist.github.com/ZeGentzy/20398fb571ca5f73e08c00338ffb669a Based off this commit: goddessfreya/glutin@1defedf
Running Running |
Triage: tagging P-high and unnominating (nomination was, AFAICT, a request for prioritization). |
Upgrading to 2019-04-11 has fixed this for me! Happy to finally be able to use incremental builds again :) |
Do I dare tag this as E-needstest? It might be plausible to turn the notes above into a test in Tagging as E-needstest and assigning to self; if its too hard, I'll just close as fixed and not worry about the test. |
triage: downgrading to P-medium under assumption that this is fixed and just "needs" a test (where "needs" should really be "kinda wants but doesn't need") |
#60697 added a test for this issue. |
This went away after a
cargo clean
. I'm sorry I can't reproduce this anymore. Also this was with a stage 1 compiler so who knows if it's real.The code I was compiling:
The text was updated successfully, but these errors were encountered: