Dec 15 16:56:07.252 INFO testing dire-0.3.1 against master#bd47d6825bf4090517549d33cfef10d3300b4a75 for pr-56550 Dec 15 16:56:07.252 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-7/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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:56:07.755 INFO [stdout] 78a3727432c5c892b9ea90f32df57a8d0053666a855dae1f77a12821e0dc4661 Dec 15 16:56:07.757 INFO running `"docker" "start" "-a" "78a3727432c5c892b9ea90f32df57a8d0053666a855dae1f77a12821e0dc4661"` Dec 15 16:56:09.906 INFO [stderr] usermod: no changes Dec 15 16:56:09.951 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 15 16:56:09.951 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 15 16:56:09.951 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 15 16:56:09.951 INFO [stderr] files will be included as a binary target: Dec 15 16:56:09.951 INFO [stderr] Dec 15 16:56:09.951 INFO [stderr] * /source/src/main.rs Dec 15 16:56:09.951 INFO [stderr] Dec 15 16:56:09.951 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 15 16:56:09.951 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 15 16:56:09.951 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 15 16:56:09.951 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 15 16:56:09.951 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 15 16:56:09.951 INFO [stderr] Dec 15 16:56:09.951 INFO [stderr] For more information on this warning you can consult Dec 15 16:56:09.951 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 15 16:56:09.951 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`, Dec 15 16:56:09.951 INFO [stderr] please set bin.path in Cargo.toml Dec 15 16:56:09.969 INFO [stderr] Compiling dire v0.3.1 (/source) Dec 15 16:56:10.583 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. Dec 15 16:56:10.583 INFO [stderr] --> src/unix.rs:21:24 Dec 15 16:56:10.583 INFO [stderr] | Dec 15 16:56:10.583 INFO [stderr] 21 | let home = env::home_dir().ok_or(DirsError::HomeMissing)?; Dec 15 16:56:10.583 INFO [stderr] | ^^^^^^^^^^^^^ Dec 15 16:56:10.583 INFO [stderr] | Dec 15 16:56:10.583 INFO [stderr] = note: #[warn(deprecated)] on by default Dec 15 16:56:10.584 INFO [stderr] Dec 15 16:56:11.934 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.00s Dec 15 16:56:11.938 INFO [stderr] su: No module specific data is present Dec 15 16:56:12.807 INFO running `"docker" "inspect" "78a3727432c5c892b9ea90f32df57a8d0053666a855dae1f77a12821e0dc4661"` Dec 15 16:56:13.163 INFO running `"docker" "rm" "-f" "78a3727432c5c892b9ea90f32df57a8d0053666a855dae1f77a12821e0dc4661"` Dec 15 16:56:13.503 INFO [stdout] 78a3727432c5c892b9ea90f32df57a8d0053666a855dae1f77a12821e0dc4661 Dec 15 16:56:13.507 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-7/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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:56:13.950 INFO [stdout] 572f21237af9020be5679fccaa1b102592780924a84801dfcc6187f50e5566b3 Dec 15 16:56:13.952 INFO running `"docker" "start" "-a" "572f21237af9020be5679fccaa1b102592780924a84801dfcc6187f50e5566b3"` Dec 15 16:56:15.532 INFO [stderr] usermod: no changes Dec 15 16:56:15.575 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 15 16:56:15.575 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 15 16:56:15.575 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 15 16:56:15.575 INFO [stderr] files will be included as a binary target: Dec 15 16:56:15.575 INFO [stderr] Dec 15 16:56:15.575 INFO [stderr] * /source/src/main.rs Dec 15 16:56:15.575 INFO [stderr] Dec 15 16:56:15.575 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 15 16:56:15.575 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 15 16:56:15.575 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 15 16:56:15.575 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 15 16:56:15.575 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 15 16:56:15.575 INFO [stderr] Dec 15 16:56:15.575 INFO [stderr] For more information on this warning you can consult Dec 15 16:56:15.575 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 15 16:56:15.575 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`, Dec 15 16:56:15.575 INFO [stderr] please set bin.path in Cargo.toml Dec 15 16:56:15.585 INFO [stderr] Compiling dire v0.3.1 (/source) Dec 15 16:56:16.667 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. Dec 15 16:56:16.667 INFO [stderr] --> src/unix.rs:21:24 Dec 15 16:56:16.667 INFO [stderr] | Dec 15 16:56:16.667 INFO [stderr] 21 | let home = env::home_dir().ok_or(DirsError::HomeMissing)?; Dec 15 16:56:16.667 INFO [stderr] | ^^^^^^^^^^^^^ Dec 15 16:56:16.667 INFO [stderr] | Dec 15 16:56:16.667 INFO [stderr] = note: #[warn(deprecated)] on by default Dec 15 16:56:16.667 INFO [stderr] Dec 15 16:56:17.218 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.66s Dec 15 16:56:17.222 INFO [stderr] su: No module specific data is present Dec 15 16:56:17.800 INFO running `"docker" "inspect" "572f21237af9020be5679fccaa1b102592780924a84801dfcc6187f50e5566b3"` Dec 15 16:56:18.013 INFO running `"docker" "rm" "-f" "572f21237af9020be5679fccaa1b102592780924a84801dfcc6187f50e5566b3"` Dec 15 16:56:18.475 INFO [stdout] 572f21237af9020be5679fccaa1b102592780924a84801dfcc6187f50e5566b3 Dec 15 16:56:18.483 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-7/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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" "-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:56:19.000 INFO [stdout] 5dba9bced485be7a8e6bef6dc6f87d2c4426da424dc3567370ccf12993368e4e Dec 15 16:56:19.003 INFO running `"docker" "start" "-a" "5dba9bced485be7a8e6bef6dc6f87d2c4426da424dc3567370ccf12993368e4e"` Dec 15 16:56:20.433 INFO [stderr] usermod: no changes Dec 15 16:56:20.499 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 15 16:56:20.499 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 15 16:56:20.499 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 15 16:56:20.499 INFO [stderr] files will be included as a binary target: Dec 15 16:56:20.499 INFO [stderr] Dec 15 16:56:20.499 INFO [stderr] * /source/src/main.rs Dec 15 16:56:20.499 INFO [stderr] Dec 15 16:56:20.499 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 15 16:56:20.499 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 15 16:56:20.499 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 15 16:56:20.499 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 15 16:56:20.499 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 15 16:56:20.499 INFO [stderr] Dec 15 16:56:20.499 INFO [stderr] For more information on this warning you can consult Dec 15 16:56:20.499 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 15 16:56:20.499 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`, Dec 15 16:56:20.499 INFO [stderr] please set bin.path in Cargo.toml Dec 15 16:56:20.508 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.04s Dec 15 16:56:20.515 INFO [stderr] Running /target/debug/deps/dire-fc59aa4cca00d04a Dec 15 16:56:20.515 INFO [stdout] Dec 15 16:56:20.515 INFO [stdout] running 0 tests Dec 15 16:56:20.515 INFO [stdout] Dec 15 16:56:20.515 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 15 16:56:20.515 INFO [stdout] Dec 15 16:56:20.520 INFO [stdout] Dec 15 16:56:20.520 INFO [stderr] Running /target/debug/deps/dirs-f396e6c3a2d640af Dec 15 16:56:20.520 INFO [stdout] running 0 tests Dec 15 16:56:20.520 INFO [stdout] Dec 15 16:56:20.520 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 15 16:56:20.520 INFO [stdout] Dec 15 16:56:20.527 INFO [stderr] Doc-tests dire Dec 15 16:56:21.619 INFO [stdout] Dec 15 16:56:21.619 INFO [stdout] running 0 tests Dec 15 16:56:21.619 INFO [stdout] Dec 15 16:56:21.619 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 15 16:56:21.619 INFO [stdout] Dec 15 16:56:21.626 INFO [stderr] su: No module specific data is present Dec 15 16:56:22.722 INFO running `"docker" "inspect" "5dba9bced485be7a8e6bef6dc6f87d2c4426da424dc3567370ccf12993368e4e"` Dec 15 16:56:22.984 INFO running `"docker" "rm" "-f" "5dba9bced485be7a8e6bef6dc6f87d2c4426da424dc3567370ccf12993368e4e"` Dec 15 16:56:23.307 INFO [stdout] 5dba9bced485be7a8e6bef6dc6f87d2c4426da424dc3567370ccf12993368e4e