Repository navigation
Compiler panic when running 'cargo check' with missing crate #40757
Description
With both current stable and nightly...
$ rustup update nightly
$ rustup override set nightly
$ rustc --version
rustc 1.17.0-nightly (8c4f2c64c 2017-03-22)
...when compiling this crate...
[package]
name = "crash"
version = "0.1.0"
[dependencies]
diesel = { version = "0.11.0", features = ["postgres", "chrono"] }
diesel_codegen = { version = "0.11.0", features = ["postgres"] }// src/main.rs
#[macro_use] extern crate diesel;
#[macro_use] extern crate diesel_codegen;
extern crate chrono;
use chrono::{DateTime, UTC};
#[derive(Queryable, Debug)]
struct Foo {
bar: u32,
date: DateTime<UTC>,
}
fn main() {
println!("Hello, world!");
}...the compiler crashes on cargo check:
$ cargo check
Compiling crash v0.1.0 (file:///tmp/crash)
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
thread 'rustc' panicked at 'called `Option::unwrap()` on a `None` value', /checkout/src/libcore/option.rs:329
note: Run with `RUST_BACKTRACE=1` for a backtrace.
error: Could not compile `crash`.
To learn more, run the command again with --verbose.
Here's the backtrace:
thread 'rustc' panicked at 'called `Option::unwrap()` on a `None` value', /checkout/src/libcore/option.rs:329
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
0: rustc_metadata::creader::CrateLoader::resolve_crate
1: <rustc_metadata::creader::CrateLoader<'a> as rustc::middle::cstore::CrateLoader>::process_item
2: rustc_resolve::build_reduced_graph::<impl rustc_resolve::Resolver<'a>>::build_reduced_graph_for_item
3: <rustc_resolve::build_reduced_graph::BuildReducedGraphVisitor<'a, 'b> as syntax::visit::Visitor<'a>>::visit_item
4: <rustc_resolve::build_reduced_graph::BuildReducedGraphVisitor<'a, 'b> as syntax::visit::Visitor<'a>>::visit_item
5: rustc_resolve::macros::<impl syntax::ext::base::Resolver for rustc_resolve::Resolver<'a>>::visit_expansion
6: syntax::ext::expand::MacroExpander::collect_invocations
7: syntax::ext::expand::MacroExpander::expand
8: syntax::ext::expand::MacroExpander::expand_crate
9: rustc_driver::driver::phase_2_configure_and_expand::{{closure}}
10: rustc_driver::driver::phase_2_configure_and_expand
11: rustc_driver::driver::compile_input
12: rustc_driver::run_compiler
13: std::panicking::try::do_call
14: __rust_maybe_catch_panic
at /checkout/src/libpanic_unwind/lib.rs:98
15: <F as alloc::boxed::FnBox<A>>::call_box
16: std::sys::imp::thread::Thread::new::thread_start
at /checkout/src/liballoc/boxed.rs:650
at /checkout/src/libstd/sys_common/thread.rs:21
at /checkout/src/libstd/sys/unix/thread.rs:84
17: start_thread
18: clone
The problem does not happen when using cargo run:
$ cargo run
Compiling crash v0.1.0 (file:///tmp/crash)
error[E0463]: can't find crate for `chrono`
--> src/main.rs:3:1
|
3 | extern crate chrono;
| ^^^^^^^^^^^^^^^^^^^^ can't find crate
error: aborting due to previous error
error: Could not compile `crash`.
Might be related to #40755.
Activity
abonander commentedon Mar 25, 2017
Should have been fixed with #40542, please try again with a newer nightly (when one is available) and let me know if it still happens.
dbrgn commentedon Mar 25, 2017
@abonander just tested it on current nightly (3da4023 2017-03-24), bug seems fixed! Thank you! ✨
mkollaro commentedon Mar 25, 2017
I got this issue with
cargo checkon stable Rust. I was removing a dependency, but forgot to deleteextern crate Xfrom main.rs, while I already deleted it from Cargo.toml. Thecargo checkcommand panics because of this, butcargo builddoesn't have the issue and correctly complained that I don't have crate X.Using rustc 1.16.0 (30cf806 2017-03-10) and cargo-0.17.0-nightly (f9e5481 2017-03-03).
dbrgn commentedon Mar 25, 2017
@mkollaro try upgrading to nightly 2017-03-24 (
rustup update nightly).mkollaro commentedon Mar 25, 2017
Got fixed 5 seconds before I added my comment...well it doesn't really trouble me, I can use
cargo checkonce I remove theextern cratethat shouldn't have been there.For those who hit against this issue before it lands in stable: just run
cargo build, fix the error, then runcargo checkagain.