Dec 03 18:00:04.978 INFO testing ble-0.1.1 against 1.30.1 for beta-1.31-5
Dec 03 18:00:04.978 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-7/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/beta-1.31-5/1.30.1:/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 +1.30.1 build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 18:00:05.279 INFO [stdout] 03159a507c2d3c03e95232972c1415a9d5bece0f85e3415b5bb731fef8c45df5
Dec 03 18:00:05.279 INFO running `"docker" "start" "-a" "03159a507c2d3c03e95232972c1415a9d5bece0f85e3415b5bb731fef8c45df5"`
Dec 03 18:00:05.745 INFO [stderr] usermod: no changes
Dec 03 18:00:05.771 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 18:00:05.771 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 18:00:05.771 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 18:00:05.771 INFO [stderr] files will be included as a binary target:
Dec 03 18:00:05.771 INFO [stderr] 
Dec 03 18:00:05.771 INFO [stderr] * /source/src/main.rs
Dec 03 18:00:05.771 INFO [stderr] 
Dec 03 18:00:05.771 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 18:00:05.771 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 18:00:05.771 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 18:00:05.771 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 18:00:05.771 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 18:00:05.771 INFO [stderr] 
Dec 03 18:00:05.771 INFO [stderr] For more information on this warning you can consult
Dec 03 18:00:05.771 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 18:00:05.771 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `ble-scan`,
Dec 03 18:00:05.771 INFO [stderr] please set bin.path in Cargo.toml
Dec 03 18:00:05.797 INFO [stderr]    Compiling ble v0.1.1 (/source)
Dec 03 18:00:08.524 INFO [stderr] error[E0554]: #![feature] may not be used on the stable release channel
Dec 03 18:00:08.524 INFO [stderr]  --> src/main.rs:1:1
Dec 03 18:00:08.524 INFO [stderr]   |
Dec 03 18:00:08.524 INFO [stderr] 1 | #![feature(alloc_system)]
Dec 03 18:00:08.524 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 03 18:00:08.524 INFO [stderr] 
Dec 03 18:00:08.524 INFO [stderr] error: aborting due to previous error
Dec 03 18:00:08.524 INFO [stderr] 
Dec 03 18:00:08.524 INFO [stderr] For more information about this error, try `rustc --explain E0554`.
Dec 03 18:00:08.529 INFO [stderr] error: Could not compile `ble`.
Dec 03 18:00:08.529 INFO [stderr] 
Dec 03 18:00:08.529 INFO [stderr] To learn more, run the command again with --verbose.
Dec 03 18:00:08.530 INFO [stderr] su: No module specific data is present
Dec 03 18:00:08.864 INFO running `"docker" "inspect" "03159a507c2d3c03e95232972c1415a9d5bece0f85e3415b5bb731fef8c45df5"`
Dec 03 18:00:08.985 INFO running `"docker" "rm" "-f" "03159a507c2d3c03e95232972c1415a9d5bece0f85e3415b5bb731fef8c45df5"`
Dec 03 18:00:09.187 INFO [stdout] 03159a507c2d3c03e95232972c1415a9d5bece0f85e3415b5bb731fef8c45df5