Dec 07 18:17:41.529 INFO testing du-0.1.1 against master#906deae0790bd18681b937fe9a141a3c26cf1855 for pr-56514
Dec 07 18:17:41.529 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-3/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56514/master#906deae0790bd18681b937fe9a141a3c26cf1855:/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 +906deae0790bd18681b937fe9a141a3c26cf1855-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 07 18:17:41.820 INFO [stdout] ae0b25318ce12dae5d6a066ae68f76334cfc625547b58087b2a3814a37c1edc1
Dec 07 18:17:41.826 INFO running `"docker" "start" "-a" "ae0b25318ce12dae5d6a066ae68f76334cfc625547b58087b2a3814a37c1edc1"`
Dec 07 18:17:42.221 INFO [stderr] usermod: no changes
Dec 07 18:17:42.256 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 07 18:17:42.256 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 07 18:17:42.256 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 07 18:17:42.256 INFO [stderr] files will be included as a binary target:
Dec 07 18:17:42.256 INFO [stderr] 
Dec 07 18:17:42.256 INFO [stderr] * /source/src/main.rs
Dec 07 18:17:42.256 INFO [stderr] 
Dec 07 18:17:42.256 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 07 18:17:42.256 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 07 18:17:42.256 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 07 18:17:42.256 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 07 18:17:42.256 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 07 18:17:42.256 INFO [stderr] 
Dec 07 18:17:42.256 INFO [stderr] For more information on this warning you can consult
Dec 07 18:17:42.256 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 07 18:17:42.256 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-du`,
Dec 07 18:17:42.256 INFO [stderr] please set bin.path in Cargo.toml
Dec 07 18:17:42.277 INFO [stderr]    Compiling du v0.1.1 (/source)
Dec 07 18:17:44.039 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.79s
Dec 07 18:17:44.044 INFO [stderr] su: No module specific data is present
Dec 07 18:17:44.375 INFO running `"docker" "inspect" "ae0b25318ce12dae5d6a066ae68f76334cfc625547b58087b2a3814a37c1edc1"`
Dec 07 18:17:44.492 INFO running `"docker" "rm" "-f" "ae0b25318ce12dae5d6a066ae68f76334cfc625547b58087b2a3814a37c1edc1"`
Dec 07 18:17:44.664 INFO [stdout] ae0b25318ce12dae5d6a066ae68f76334cfc625547b58087b2a3814a37c1edc1
Dec 07 18:17:44.670 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-3/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56514/master#906deae0790bd18681b937fe9a141a3c26cf1855:/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 +906deae0790bd18681b937fe9a141a3c26cf1855-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"`
Dec 07 18:17:44.915 INFO [stdout] f3ebc52b391efc38e9feed0e25292915cce6d4e08186c1b05da82349b5d9ffda
Dec 07 18:17:44.918 INFO running `"docker" "start" "-a" "f3ebc52b391efc38e9feed0e25292915cce6d4e08186c1b05da82349b5d9ffda"`
Dec 07 18:17:45.433 INFO [stderr] usermod: no changes
Dec 07 18:17:45.504 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 07 18:17:45.504 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 07 18:17:45.504 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 07 18:17:45.504 INFO [stderr] files will be included as a binary target:
Dec 07 18:17:45.504 INFO [stderr] 
Dec 07 18:17:45.504 INFO [stderr] * /source/src/main.rs
Dec 07 18:17:45.504 INFO [stderr] 
Dec 07 18:17:45.504 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 07 18:17:45.504 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 07 18:17:45.504 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 07 18:17:45.504 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 07 18:17:45.504 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 07 18:17:45.504 INFO [stderr] 
Dec 07 18:17:45.504 INFO [stderr] For more information on this warning you can consult
Dec 07 18:17:45.504 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 07 18:17:45.504 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-du`,
Dec 07 18:17:45.504 INFO [stderr] please set bin.path in Cargo.toml
Dec 07 18:17:45.520 INFO [stderr]    Compiling du v0.1.1 (/source)
Dec 07 18:17:46.895 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.40s
Dec 07 18:17:46.896 INFO [stderr] su: No module specific data is present
Dec 07 18:17:47.151 INFO running `"docker" "inspect" "f3ebc52b391efc38e9feed0e25292915cce6d4e08186c1b05da82349b5d9ffda"`
Dec 07 18:17:47.234 INFO running `"docker" "rm" "-f" "f3ebc52b391efc38e9feed0e25292915cce6d4e08186c1b05da82349b5d9ffda"`
Dec 07 18:17:47.339 INFO [stdout] f3ebc52b391efc38e9feed0e25292915cce6d4e08186c1b05da82349b5d9ffda