Aug 02 13:58:40.997 INFO checking ble-0.1.1 against 1.27.2+tmplazy for lazy_static-1 Aug 02 13:58:40.997 INFO running: cargo +1.27.2 check --frozen --all --all-targets Aug 02 13:58:40.997 INFO creating container for: cargo +1.27.2 check --frozen --all --all-targets Aug 02 13:58:40.997 INFO running `"docker" "create" "-v" "/tmp/crater.YULVrTwRoVUY:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/lazy_static-1/worker-0/1.27.2+tmplazy:/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 02 13:58:41.244 INFO blam! f949d99771a75e614342252f8c6239a75d5125f4b2e758e96108f414682e8884 Aug 02 13:58:41.246 INFO running `"docker" "start" "-a" "f949d99771a75e614342252f8c6239a75d5125f4b2e758e96108f414682e8884"` Aug 02 13:58:42.285 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently Aug 02 13:58:42.285 INFO kablam! disables Cargo from automatically inferring other binary targets. Aug 02 13:58:42.286 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Aug 02 13:58:42.286 INFO kablam! files will be included as a binary target: Aug 02 13:58:42.286 INFO kablam! Aug 02 13:58:42.286 INFO kablam! * /source/src/main.rs Aug 02 13:58:42.286 INFO kablam! Aug 02 13:58:42.286 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Aug 02 13:58:42.286 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself Aug 02 13:58:42.286 INFO kablam! and disable this warning by adding `autobins = false` to your [package] Aug 02 13:58:42.286 INFO kablam! section. You may also move the files to a location where Cargo would not Aug 02 13:58:42.286 INFO kablam! automatically infer them to be a target, such as in subfolders. Aug 02 13:58:42.286 INFO kablam! Aug 02 13:58:42.286 INFO kablam! For more information on this warning you can consult Aug 02 13:58:42.286 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Aug 02 13:58:42.286 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `ble-scan`, Aug 02 13:58:42.286 INFO kablam! please set bin.path in Cargo.toml Aug 02 13:58:42.326 INFO kablam! Checking ble v0.1.1 (file:///source) Aug 02 13:58:45.033 INFO kablam! error[E0554]: #![feature] may not be used on the stable release channel Aug 02 13:58:45.033 INFO kablam! --> src/main.rs:1:1 Aug 02 13:58:45.033 INFO kablam! | Aug 02 13:58:45.033 INFO kablam! 1 | #![feature(alloc_system)] Aug 02 13:58:45.033 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 02 13:58:45.033 INFO kablam! Aug 02 13:58:45.033 INFO kablam! error: aborting due to previous error Aug 02 13:58:45.034 INFO kablam! Aug 02 13:58:45.034 INFO kablam! For more information about this error, try `rustc --explain E0554`. Aug 02 13:58:45.041 INFO kablam! error: Could not compile `ble`. Aug 02 13:58:45.041 INFO kablam! warning: build failed, waiting for other jobs to finish... Aug 02 13:58:45.160 INFO kablam! error[E0554]: #![feature] may not be used on the stable release channel Aug 02 13:58:45.160 INFO kablam! --> src/main.rs:1:1 Aug 02 13:58:45.160 INFO kablam! | Aug 02 13:58:45.160 INFO kablam! 1 | #![feature(alloc_system)] Aug 02 13:58:45.160 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^ Aug 02 13:58:45.160 INFO kablam! Aug 02 13:58:45.160 INFO kablam! error: aborting due to previous error Aug 02 13:58:45.160 INFO kablam! Aug 02 13:58:45.160 INFO kablam! For more information about this error, try `rustc --explain E0554`. Aug 02 13:58:45.173 INFO kablam! error: Could not compile `ble`. Aug 02 13:58:45.174 INFO kablam! Aug 02 13:58:45.174 INFO kablam! To learn more, run the command again with --verbose. Aug 02 13:58:45.193 INFO kablam! su: No module specific data is present Aug 02 13:58:46.238 INFO running `"docker" "rm" "-f" "f949d99771a75e614342252f8c6239a75d5125f4b2e758e96108f414682e8884"` Aug 02 13:58:46.397 INFO blam! f949d99771a75e614342252f8c6239a75d5125f4b2e758e96108f414682e8884