Nov 29 02:23:10.364 INFO checking dire-0.3.1 against try#db42d4dad33013eba11ef37342ad9f614e5652b8 for pr-56074 Nov 29 02:23:10.364 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-6/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56074/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/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 +db42d4dad33013eba11ef37342ad9f614e5652b8-alt check --frozen --all --all-targets" "-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 29 02:23:10.559 INFO [stdout] 3ddfa87b6dc023015fafb4ee703df6a2d30ac6260da54c6da9f1874659a42bf5 Nov 29 02:23:10.563 INFO running `"docker" "start" "-a" "3ddfa87b6dc023015fafb4ee703df6a2d30ac6260da54c6da9f1874659a42bf5"` Nov 29 02:23:11.584 INFO [stderr] usermod: no changes Nov 29 02:23:11.624 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 29 02:23:11.624 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 29 02:23:11.624 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 29 02:23:11.624 INFO [stderr] files will be included as a binary target: Nov 29 02:23:11.624 INFO [stderr] Nov 29 02:23:11.624 INFO [stderr] * /source/src/main.rs Nov 29 02:23:11.624 INFO [stderr] Nov 29 02:23:11.624 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 29 02:23:11.624 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 29 02:23:11.624 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 29 02:23:11.624 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 29 02:23:11.624 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 29 02:23:11.624 INFO [stderr] Nov 29 02:23:11.624 INFO [stderr] For more information on this warning you can consult Nov 29 02:23:11.624 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 29 02:23:11.624 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`, Nov 29 02:23:11.624 INFO [stderr] please set bin.path in Cargo.toml Nov 29 02:23:11.640 INFO [stderr] Checking dire v0.3.1 (/source) Nov 29 02:23:12.272 INFO [stderr] warning: use of deprecated item 'std::env::home_dir': This function's behavior is unexpected and probably not what you want. Consider using the home_dir function from https://crates.io/crates/dirs instead. Nov 29 02:23:12.272 INFO [stderr] --> src/unix.rs:21:24 Nov 29 02:23:12.272 INFO [stderr] | Nov 29 02:23:12.272 INFO [stderr] 21 | let home = env::home_dir().ok_or(DirsError::HomeMissing)?; Nov 29 02:23:12.272 INFO [stderr] | ^^^^^^^^^^^^^ Nov 29 02:23:12.272 INFO [stderr] | Nov 29 02:23:12.272 INFO [stderr] = note: #[warn(deprecated)] on by default Nov 29 02:23:12.272 INFO [stderr] Nov 29 02:23:12.516 INFO [stderr] warning: use of deprecated item 'std::env::home_dir': This function's behavior is unexpected and probably not what you want. Consider using the home_dir function from https://crates.io/crates/dirs instead. Nov 29 02:23:12.516 INFO [stderr] --> src/unix.rs:21:24 Nov 29 02:23:12.516 INFO [stderr] | Nov 29 02:23:12.516 INFO [stderr] 21 | let home = env::home_dir().ok_or(DirsError::HomeMissing)?; Nov 29 02:23:12.516 INFO [stderr] | ^^^^^^^^^^^^^ Nov 29 02:23:12.516 INFO [stderr] | Nov 29 02:23:12.516 INFO [stderr] = note: #[warn(deprecated)] on by default Nov 29 02:23:12.516 INFO [stderr] Nov 29 02:23:13.162 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.55s Nov 29 02:23:13.165 INFO [stderr] su: No module specific data is present Nov 29 02:23:13.525 INFO running `"docker" "inspect" "3ddfa87b6dc023015fafb4ee703df6a2d30ac6260da54c6da9f1874659a42bf5"` Nov 29 02:23:13.597 INFO running `"docker" "rm" "-f" "3ddfa87b6dc023015fafb4ee703df6a2d30ac6260da54c6da9f1874659a42bf5"` Nov 29 02:23:13.675 INFO [stdout] 3ddfa87b6dc023015fafb4ee703df6a2d30ac6260da54c6da9f1874659a42bf5