Aug 01 19:23:50.260 INFO checking varianteq-0.4.1 against 1.27.2 for lazy_static-1 Aug 01 19:23:50.260 INFO running: cargo +1.27.2 check --frozen --all --all-targets Aug 01 19:23:50.260 INFO creating container for: cargo +1.27.2 check --frozen --all --all-targets Aug 01 19:23:50.260 INFO running `"docker" "create" "-v" "/tmp/crater.qTMd3quON81r:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/lazy_static-1/worker-2/1.27.2:/target:rw,Z" "-v" "/home/ec2-user/crater/./work/local/cargo-home:/cargo-home:ro,Z" "-v" "/home/ec2-user/crater/./work/local/rustup-home:/rustup-home:ro,Z" "-v" "/home/ec2-user/crater/./work/local/cargo-home/git:/cargo-home/git:rw,Z" "-e" "USER_ID=500" "-e" "CMD=cargo +1.27.2 check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "crater"` Aug 01 19:23:50.518 INFO blam! 0dd3c47abf8664665aa2a4b56aaaaf7f363341499fb86a9f4307a51ee33a3f67 Aug 01 19:23:50.520 INFO running `"docker" "start" "-a" "0dd3c47abf8664665aa2a4b56aaaaf7f363341499fb86a9f4307a51ee33a3f67"` Aug 01 19:23:51.621 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently Aug 01 19:23:51.621 INFO kablam! disables Cargo from automatically inferring other test targets. Aug 01 19:23:51.621 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Aug 01 19:23:51.621 INFO kablam! files will be included as a test target: Aug 01 19:23:51.621 INFO kablam! Aug 01 19:23:51.621 INFO kablam! * /source/tests/generic.rs Aug 01 19:23:51.621 INFO kablam! Aug 01 19:23:51.621 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Aug 01 19:23:51.621 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself Aug 01 19:23:51.621 INFO kablam! and disable this warning by adding `autotests = false` to your [package] Aug 01 19:23:51.621 INFO kablam! section. You may also move the files to a location where Cargo would not Aug 01 19:23:51.621 INFO kablam! automatically infer them to be a target, such as in subfolders. Aug 01 19:23:51.621 INFO kablam! Aug 01 19:23:51.621 INFO kablam! For more information on this warning you can consult Aug 01 19:23:51.621 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Aug 01 19:23:51.671 INFO kablam! Checking proc-macro2 v0.3.8 Aug 01 19:23:51.672 INFO kablam! Compiling syn v0.13.11 Aug 01 19:23:54.343 INFO kablam! Checking quote v0.5.2 Aug 01 19:24:06.644 INFO kablam! Checking varianteq v0.4.1 (file:///source) Aug 01 19:24:08.395 INFO kablam! error[E0554]: #![feature] may not be used on the stable release channel Aug 01 19:24:08.395 INFO kablam! --> src/lib.rs:57:1 Aug 01 19:24:08.395 INFO kablam! | Aug 01 19:24:08.395 INFO kablam! 57 | #![feature(proc_macro)] Aug 01 19:24:08.395 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^ Aug 01 19:24:08.395 INFO kablam! Aug 01 19:24:08.396 INFO kablam! error: aborting due to previous error Aug 01 19:24:08.397 INFO kablam! Aug 01 19:24:08.397 INFO kablam! For more information about this error, try `rustc --explain E0554`. Aug 01 19:24:08.435 INFO kablam! error: Could not compile `varianteq`. Aug 01 19:24:08.441 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 01 19:24:08.691 INFO kablam! error[E0554]: #![feature] may not be used on the stable release channel Aug 01 19:24:08.691 INFO kablam! --> src/lib.rs:57:1 Aug 01 19:24:08.691 INFO kablam! | Aug 01 19:24:08.691 INFO kablam! 57 | #![feature(proc_macro)] Aug 01 19:24:08.691 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^ Aug 01 19:24:08.691 INFO kablam! Aug 01 19:24:08.691 INFO kablam! error: aborting due to previous error Aug 01 19:24:08.691 INFO kablam! Aug 01 19:24:08.691 INFO kablam! For more information about this error, try `rustc --explain E0554`. Aug 01 19:24:08.703 INFO kablam! error: Could not compile `varianteq`. Aug 01 19:24:08.704 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 01 19:24:11.486 INFO kablam! error: build failed Aug 01 19:24:11.488 INFO kablam! su: No module specific data is present Aug 01 19:24:12.070 INFO running `"docker" "rm" "-f" "0dd3c47abf8664665aa2a4b56aaaaf7f363341499fb86a9f4307a51ee33a3f67"` Aug 01 19:24:12.269 INFO blam! 0dd3c47abf8664665aa2a4b56aaaaf7f363341499fb86a9f4307a51ee33a3f67