Nov 18 19:26:59.659 INFO testing ble-0.1.1 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 19:26:59.659 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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"`
Nov 18 19:26:59.944 INFO [stdout] 8d8483eb9f5832c9e55590674e4406f311d607a661399236e29e940fd738e42c
Nov 18 19:26:59.946 INFO running `"docker" "start" "-a" "8d8483eb9f5832c9e55590674e4406f311d607a661399236e29e940fd738e42c"`
Nov 18 19:27:00.893 INFO [stderr] usermod: no changes
Nov 18 19:27:00.934 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 19:27:00.934 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 19:27:00.934 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 19:27:00.934 INFO [stderr] files will be included as a binary target:
Nov 18 19:27:00.934 INFO [stderr] 
Nov 18 19:27:00.934 INFO [stderr] * /source/src/main.rs
Nov 18 19:27:00.934 INFO [stderr] 
Nov 18 19:27:00.934 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 19:27:00.934 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 19:27:00.934 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 19:27:00.934 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 19:27:00.934 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 19:27:00.934 INFO [stderr] 
Nov 18 19:27:00.935 INFO [stderr] For more information on this warning you can consult
Nov 18 19:27:00.935 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 19:27:00.935 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `ble-scan`,
Nov 18 19:27:00.935 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 19:27:00.967 INFO [stderr]    Compiling ble v0.1.1 (/source)
Nov 18 19:27:02.630 INFO [stderr] error[E0463]: can't find crate for `alloc_system`
Nov 18 19:27:02.631 INFO [stderr]  --> src/main.rs:3:1
Nov 18 19:27:02.631 INFO [stderr]   |
Nov 18 19:27:02.631 INFO [stderr] 3 | extern crate alloc_system;
Nov 18 19:27:02.631 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate
Nov 18 19:27:02.631 INFO [stderr] 
Nov 18 19:27:02.640 INFO [stderr] error: aborting due to previous error
Nov 18 19:27:02.640 INFO [stderr] 
Nov 18 19:27:02.640 INFO [stderr] For more information about this error, try `rustc --explain E0463`.
Nov 18 19:27:02.646 INFO [stderr] error: Could not compile `ble`.
Nov 18 19:27:02.646 INFO [stderr] 
Nov 18 19:27:02.646 INFO [stderr] To learn more, run the command again with --verbose.
Nov 18 19:27:02.648 INFO [stderr] su: No module specific data is present
Nov 18 19:27:02.948 INFO running `"docker" "inspect" "8d8483eb9f5832c9e55590674e4406f311d607a661399236e29e940fd738e42c"`
Nov 18 19:27:03.041 INFO running `"docker" "rm" "-f" "8d8483eb9f5832c9e55590674e4406f311d607a661399236e29e940fd738e42c"`
Nov 18 19:27:03.151 INFO [stdout] 8d8483eb9f5832c9e55590674e4406f311d607a661399236e29e940fd738e42c