Nov 18 15:41:15.230 INFO testing du-0.1.1 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 15:41:15.236 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 15:41:15.509 INFO [stdout] 0c455b86cd14c306de9962156a425c6398f0dc5a0ab2675400929557404397dc
Nov 18 15:41:15.512 INFO running `"docker" "start" "-a" "0c455b86cd14c306de9962156a425c6398f0dc5a0ab2675400929557404397dc"`
Nov 18 15:41:15.855 INFO [stderr] usermod: no changes
Nov 18 15:41:15.890 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 15:41:15.890 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 15:41:15.890 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 15:41:15.890 INFO [stderr] files will be included as a binary target:
Nov 18 15:41:15.890 INFO [stderr] 
Nov 18 15:41:15.890 INFO [stderr] * /source/src/main.rs
Nov 18 15:41:15.890 INFO [stderr] 
Nov 18 15:41:15.890 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 15:41:15.890 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 15:41:15.890 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 15:41:15.890 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 15:41:15.890 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 15:41:15.890 INFO [stderr] 
Nov 18 15:41:15.890 INFO [stderr] For more information on this warning you can consult
Nov 18 15:41:15.890 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 15:41:15.890 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-du`,
Nov 18 15:41:15.890 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 15:41:15.919 INFO [stderr]    Compiling du v0.1.1 (/source)
Nov 18 15:41:17.493 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.61s
Nov 18 15:41:17.497 INFO [stderr] su: No module specific data is present
Nov 18 15:41:17.873 INFO running `"docker" "inspect" "0c455b86cd14c306de9962156a425c6398f0dc5a0ab2675400929557404397dc"`
Nov 18 15:41:17.964 INFO running `"docker" "rm" "-f" "0c455b86cd14c306de9962156a425c6398f0dc5a0ab2675400929557404397dc"`
Nov 18 15:41:18.093 INFO [stdout] 0c455b86cd14c306de9962156a425c6398f0dc5a0ab2675400929557404397dc
Nov 18 15:41:18.100 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 test --frozen --no-run" "-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 15:41:18.351 INFO [stdout] 043fd3018299da4e0bb38fb0c525941b3b7a129dce2507c3de632aee7dc2bdcb
Nov 18 15:41:18.355 INFO running `"docker" "start" "-a" "043fd3018299da4e0bb38fb0c525941b3b7a129dce2507c3de632aee7dc2bdcb"`
Nov 18 15:41:18.902 INFO [stderr] usermod: no changes
Nov 18 15:41:18.930 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 15:41:18.930 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 15:41:18.930 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 15:41:18.930 INFO [stderr] files will be included as a binary target:
Nov 18 15:41:18.930 INFO [stderr] 
Nov 18 15:41:18.930 INFO [stderr] * /source/src/main.rs
Nov 18 15:41:18.930 INFO [stderr] 
Nov 18 15:41:18.930 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 15:41:18.930 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 15:41:18.930 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 15:41:18.930 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 15:41:18.930 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 15:41:18.930 INFO [stderr] 
Nov 18 15:41:18.930 INFO [stderr] For more information on this warning you can consult
Nov 18 15:41:18.930 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 15:41:18.930 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-du`,
Nov 18 15:41:18.930 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 15:41:18.950 INFO [stderr]    Compiling du v0.1.1 (/source)
Nov 18 15:41:20.601 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.68s
Nov 18 15:41:20.614 INFO [stderr] su: No module specific data is present
Nov 18 15:41:21.033 INFO running `"docker" "inspect" "043fd3018299da4e0bb38fb0c525941b3b7a129dce2507c3de632aee7dc2bdcb"`
Nov 18 15:41:21.124 INFO running `"docker" "rm" "-f" "043fd3018299da4e0bb38fb0c525941b3b7a129dce2507c3de632aee7dc2bdcb"`
Nov 18 15:41:21.234 INFO [stdout] 043fd3018299da4e0bb38fb0c525941b3b7a129dce2507c3de632aee7dc2bdcb