Dec 03 18:00:00.731 INFO testing ble-0.1.1 against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 03 18:00:00.732 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-6/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/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 +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt 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:00.961 INFO [stdout] 6cf2151fe039f1156c578e1ae2d037c9fe5d1b13ac1eb6b44408b345279a0420
Dec 03 18:00:00.967 INFO running `"docker" "start" "-a" "6cf2151fe039f1156c578e1ae2d037c9fe5d1b13ac1eb6b44408b345279a0420"`
Dec 03 18:00:01.863 INFO [stderr] usermod: no changes
Dec 03 18:00:01.931 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 18:00:01.931 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 18:00:01.931 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 18:00:01.931 INFO [stderr] files will be included as a binary target:
Dec 03 18:00:01.931 INFO [stderr] 
Dec 03 18:00:01.931 INFO [stderr] * /source/src/main.rs
Dec 03 18:00:01.931 INFO [stderr] 
Dec 03 18:00:01.931 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 18:00:01.931 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 18:00:01.931 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 18:00:01.931 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 18:00:01.931 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 18:00:01.931 INFO [stderr] 
Dec 03 18:00:01.931 INFO [stderr] For more information on this warning you can consult
Dec 03 18:00:01.931 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 18:00:01.931 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `ble-scan`,
Dec 03 18:00:01.931 INFO [stderr] please set bin.path in Cargo.toml
Dec 03 18:00:01.971 INFO [stderr]    Compiling ble v0.1.1 (/source)
Dec 03 18:00:04.713 INFO [stderr] error[E0554]: #![feature] may not be used on the beta release channel
Dec 03 18:00:04.713 INFO [stderr]  --> src/main.rs:1:1
Dec 03 18:00:04.714 INFO [stderr]   |
Dec 03 18:00:04.714 INFO [stderr] 1 | #![feature(alloc_system)]
Dec 03 18:00:04.714 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^
Dec 03 18:00:04.714 INFO [stderr] 
Dec 03 18:00:04.714 INFO [stderr] error: aborting due to previous error
Dec 03 18:00:04.714 INFO [stderr] 
Dec 03 18:00:04.714 INFO [stderr] For more information about this error, try `rustc --explain E0554`.
Dec 03 18:00:04.720 INFO [stderr] error: Could not compile `ble`.
Dec 03 18:00:04.720 INFO [stderr] 
Dec 03 18:00:04.720 INFO [stderr] To learn more, run the command again with --verbose.
Dec 03 18:00:04.722 INFO [stderr] su: No module specific data is present
Dec 03 18:00:05.044 INFO running `"docker" "inspect" "6cf2151fe039f1156c578e1ae2d037c9fe5d1b13ac1eb6b44408b345279a0420"`
Dec 03 18:00:05.156 INFO running `"docker" "rm" "-f" "6cf2151fe039f1156c578e1ae2d037c9fe5d1b13ac1eb6b44408b345279a0420"`
Dec 03 18:00:05.265 INFO [stdout] 6cf2151fe039f1156c578e1ae2d037c9fe5d1b13ac1eb6b44408b345279a0420