Dec 06 20:28:13.500 INFO testing tessel-0.3.1 against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514
Dec 06 20:28:13.500 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 06 20:28:13.904 INFO [stdout] 88df12be8ccaee70149e1fa89df662e2dca2f6af0e1075c8a069259d861a78c3
Dec 06 20:28:13.909 INFO running `"docker" "start" "-a" "88df12be8ccaee70149e1fa89df662e2dca2f6af0e1075c8a069259d861a78c3"`
Dec 06 20:28:14.881 INFO [stderr] usermod: no changes
Dec 06 20:28:14.936 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 06 20:28:14.936 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 06 20:28:14.936 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 06 20:28:14.936 INFO [stderr] files will be included as a binary target:
Dec 06 20:28:14.936 INFO [stderr] 
Dec 06 20:28:14.936 INFO [stderr] * /source/src/main.rs
Dec 06 20:28:14.936 INFO [stderr] 
Dec 06 20:28:14.936 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 06 20:28:14.936 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 06 20:28:14.936 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 06 20:28:14.936 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 06 20:28:14.936 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 06 20:28:14.936 INFO [stderr] 
Dec 06 20:28:14.936 INFO [stderr] For more information on this warning you can consult
Dec 06 20:28:14.936 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 06 20:28:14.936 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `hello-rust`,
Dec 06 20:28:14.936 INFO [stderr] please set bin.path in Cargo.toml
Dec 06 20:28:14.986 INFO [stderr]    Compiling atomic-option v0.1.2
Dec 06 20:28:15.344 INFO [stderr]    Compiling tessel v0.3.1 (/source)
Dec 06 20:28:16.936 INFO [stderr] error[E0463]: can't find crate for `alloc_system`
Dec 06 20:28:16.936 INFO [stderr]  --> src/main.rs:2:1
Dec 06 20:28:16.936 INFO [stderr]   |
Dec 06 20:28:16.936 INFO [stderr] 2 | extern crate alloc_system;
Dec 06 20:28:16.936 INFO [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate
Dec 06 20:28:16.936 INFO [stderr] 
Dec 06 20:28:16.936 INFO [stderr] error: aborting due to previous error
Dec 06 20:28:16.936 INFO [stderr] 
Dec 06 20:28:16.936 INFO [stderr] For more information about this error, try `rustc --explain E0463`.
Dec 06 20:28:16.952 INFO [stderr] error: Could not compile `tessel`.
Dec 06 20:28:16.952 INFO [stderr] 
Dec 06 20:28:16.952 INFO [stderr] To learn more, run the command again with --verbose.
Dec 06 20:28:16.952 INFO [stderr] su: No module specific data is present
Dec 06 20:28:17.811 INFO running `"docker" "inspect" "88df12be8ccaee70149e1fa89df662e2dca2f6af0e1075c8a069259d861a78c3"`
Dec 06 20:28:18.102 INFO running `"docker" "rm" "-f" "88df12be8ccaee70149e1fa89df662e2dca2f6af0e1075c8a069259d861a78c3"`
Dec 06 20:28:18.404 INFO [stdout] 88df12be8ccaee70149e1fa89df662e2dca2f6af0e1075c8a069259d861a78c3