Dec 15 16:31:24.812 INFO testing du-0.1.1 against master#bd47d6825bf4090517549d33cfef10d3300b4a75 for pr-56550
Dec 15 16:31:24.812 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-1/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-56550/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/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 +bd47d6825bf4090517549d33cfef10d3300b4a75-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 15 16:31:25.055 INFO [stdout] 206ff5f9327f6165e0cae9a5064aac8b40ec3da1e8f6bd0a2b98c1a70416c82d
Dec 15 16:31:25.060 INFO running `"docker" "start" "-a" "206ff5f9327f6165e0cae9a5064aac8b40ec3da1e8f6bd0a2b98c1a70416c82d"`
Dec 15 16:31:26.211 INFO [stderr] usermod: no changes
Dec 15 16:31:26.247 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 15 16:31:26.247 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 15 16:31:26.247 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 15 16:31:26.247 INFO [stderr] files will be included as a binary target:
Dec 15 16:31:26.247 INFO [stderr] 
Dec 15 16:31:26.247 INFO [stderr] * /source/src/main.rs
Dec 15 16:31:26.247 INFO [stderr] 
Dec 15 16:31:26.247 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 15 16:31:26.247 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 15 16:31:26.247 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 15 16:31:26.247 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 15 16:31:26.247 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 15 16:31:26.247 INFO [stderr] 
Dec 15 16:31:26.247 INFO [stderr] For more information on this warning you can consult
Dec 15 16:31:26.247 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 15 16:31:26.247 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-du`,
Dec 15 16:31:26.247 INFO [stderr] please set bin.path in Cargo.toml
Dec 15 16:31:26.283 INFO [stderr]    Compiling du v0.1.1 (/source)
Dec 15 16:31:28.399 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.16s
Dec 15 16:31:28.403 INFO [stderr] su: No module specific data is present
Dec 15 16:31:28.899 INFO running `"docker" "inspect" "206ff5f9327f6165e0cae9a5064aac8b40ec3da1e8f6bd0a2b98c1a70416c82d"`
Dec 15 16:31:29.149 INFO running `"docker" "rm" "-f" "206ff5f9327f6165e0cae9a5064aac8b40ec3da1e8f6bd0a2b98c1a70416c82d"`
Dec 15 16:31:29.403 INFO [stdout] 206ff5f9327f6165e0cae9a5064aac8b40ec3da1e8f6bd0a2b98c1a70416c82d
Dec 15 16:31:29.411 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-1/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-56550/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/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 +bd47d6825bf4090517549d33cfef10d3300b4a75-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 15 16:31:29.817 INFO [stdout] 41057c0c98650afd59f52a2ac53f1817c93257b2b5b1b1207cc77dbc4e7fb079
Dec 15 16:31:29.827 INFO running `"docker" "start" "-a" "41057c0c98650afd59f52a2ac53f1817c93257b2b5b1b1207cc77dbc4e7fb079"`
Dec 15 16:31:30.979 INFO [stderr] usermod: no changes
Dec 15 16:31:31.031 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 15 16:31:31.031 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 15 16:31:31.031 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 15 16:31:31.031 INFO [stderr] files will be included as a binary target:
Dec 15 16:31:31.031 INFO [stderr] 
Dec 15 16:31:31.031 INFO [stderr] * /source/src/main.rs
Dec 15 16:31:31.031 INFO [stderr] 
Dec 15 16:31:31.031 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 15 16:31:31.031 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 15 16:31:31.031 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 15 16:31:31.031 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 15 16:31:31.031 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 15 16:31:31.031 INFO [stderr] 
Dec 15 16:31:31.031 INFO [stderr] For more information on this warning you can consult
Dec 15 16:31:31.031 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 15 16:31:31.031 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-du`,
Dec 15 16:31:31.031 INFO [stderr] please set bin.path in Cargo.toml
Dec 15 16:31:31.062 INFO [stderr]    Compiling du v0.1.1 (/source)
Dec 15 16:31:32.672 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.67s
Dec 15 16:31:32.677 INFO [stderr] su: No module specific data is present
Dec 15 16:31:33.015 INFO running `"docker" "inspect" "41057c0c98650afd59f52a2ac53f1817c93257b2b5b1b1207cc77dbc4e7fb079"`
Dec 15 16:31:33.099 INFO running `"docker" "rm" "-f" "41057c0c98650afd59f52a2ac53f1817c93257b2b5b1b1207cc77dbc4e7fb079"`
Dec 15 16:31:33.231 INFO [stdout] 41057c0c98650afd59f52a2ac53f1817c93257b2b5b1b1207cc77dbc4e7fb079