Dec 07 22:28:05.687 INFO testing ble-0.1.1 against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514 Dec 07 22:28:05.687 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-5/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Dec 07 22:28:05.955 INFO [stdout] 3cd17835777a4039697349fa1ad6ee24701d38da3454a8d4b3fbc48d93b7654f Dec 07 22:28:05.957 INFO running `"docker" "start" "-a" "3cd17835777a4039697349fa1ad6ee24701d38da3454a8d4b3fbc48d93b7654f"` Dec 07 22:28:06.489 INFO [stderr] usermod: no changes Dec 07 22:28:06.513 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 07 22:28:06.513 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 07 22:28:06.513 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 22:28:06.513 INFO [stderr] files will be included as a binary target: Dec 07 22:28:06.513 INFO [stderr] Dec 07 22:28:06.513 INFO [stderr] * /source/src/main.rs Dec 07 22:28:06.513 INFO [stderr] Dec 07 22:28:06.513 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 22:28:06.513 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 07 22:28:06.513 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 07 22:28:06.513 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 22:28:06.513 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 22:28:06.513 INFO [stderr] Dec 07 22:28:06.513 INFO [stderr] For more information on this warning you can consult Dec 07 22:28:06.513 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 22:28:06.513 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `ble-scan`, Dec 07 22:28:06.513 INFO [stderr] please set bin.path in Cargo.toml Dec 07 22:28:06.544 INFO [stderr] Compiling ble v0.1.1 (/source) Dec 07 22:28:08.274 INFO [stderr] error[E0463]: can't find crate for `alloc_system` Dec 07 22:28:08.274 INFO [stderr] --> src/main.rs:3:1 Dec 07 22:28:08.274 INFO [stderr] | Dec 07 22:28:08.274 INFO [stderr] 3 | extern crate alloc_system; Dec 07 22:28:08.274 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate Dec 07 22:28:08.274 INFO [stderr] Dec 07 22:28:08.285 INFO [stderr] error: aborting due to previous error Dec 07 22:28:08.285 INFO [stderr] Dec 07 22:28:08.286 INFO [stderr] For more information about this error, try `rustc --explain E0463`. Dec 07 22:28:08.290 INFO [stderr] error: Could not compile `ble`. Dec 07 22:28:08.290 INFO [stderr] Dec 07 22:28:08.290 INFO [stderr] To learn more, run the command again with --verbose. Dec 07 22:28:08.291 INFO [stderr] su: No module specific data is present Dec 07 22:28:08.553 INFO running `"docker" "inspect" "3cd17835777a4039697349fa1ad6ee24701d38da3454a8d4b3fbc48d93b7654f"` Dec 07 22:28:08.674 INFO running `"docker" "rm" "-f" "3cd17835777a4039697349fa1ad6ee24701d38da3454a8d4b3fbc48d93b7654f"` Dec 07 22:28:08.892 INFO [stdout] 3cd17835777a4039697349fa1ad6ee24701d38da3454a8d4b3fbc48d93b7654f