Dec 07 18:41:15.629 INFO testing dire-0.3.1 against master#906deae0790bd18681b937fe9a141a3c26cf1855 for pr-56514 Dec 07 18:41:15.629 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-1/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/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:41:16.044 INFO [stdout] ea25656d7d1754c25951351057b1b01eb2e700e769b0a128cf230bbaaa89f276 Dec 07 18:41:16.047 INFO running `"docker" "start" "-a" "ea25656d7d1754c25951351057b1b01eb2e700e769b0a128cf230bbaaa89f276"` Dec 07 18:41:17.312 INFO [stderr] usermod: no changes Dec 07 18:41:17.363 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 07 18:41:17.363 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 07 18:41:17.363 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 18:41:17.363 INFO [stderr] files will be included as a binary target: Dec 07 18:41:17.363 INFO [stderr] Dec 07 18:41:17.363 INFO [stderr] * /source/src/main.rs Dec 07 18:41:17.363 INFO [stderr] Dec 07 18:41:17.363 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 18:41:17.363 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 07 18:41:17.363 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 07 18:41:17.363 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 18:41:17.363 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 18:41:17.363 INFO [stderr] Dec 07 18:41:17.363 INFO [stderr] For more information on this warning you can consult Dec 07 18:41:17.363 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 18:41:17.363 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`, Dec 07 18:41:17.363 INFO [stderr] please set bin.path in Cargo.toml Dec 07 18:41:17.376 INFO [stderr] Compiling dire v0.3.1 (/source) Dec 07 18:41:17.928 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 07 18:41:17.928 INFO [stderr] --> src/unix.rs:21:24 Dec 07 18:41:17.928 INFO [stderr] | Dec 07 18:41:17.928 INFO [stderr] 21 | let home = env::home_dir().ok_or(DirsError::HomeMissing)?; Dec 07 18:41:17.929 INFO [stderr] | ^^^^^^^^^^^^^ Dec 07 18:41:17.929 INFO [stderr] | Dec 07 18:41:17.929 INFO [stderr] = note: #[warn(deprecated)] on by default Dec 07 18:41:17.929 INFO [stderr] Dec 07 18:41:18.997 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.65s Dec 07 18:41:19.000 INFO [stderr] su: No module specific data is present Dec 07 18:41:19.654 INFO running `"docker" "inspect" "ea25656d7d1754c25951351057b1b01eb2e700e769b0a128cf230bbaaa89f276"` Dec 07 18:41:19.914 INFO running `"docker" "rm" "-f" "ea25656d7d1754c25951351057b1b01eb2e700e769b0a128cf230bbaaa89f276"` Dec 07 18:41:20.235 INFO [stdout] ea25656d7d1754c25951351057b1b01eb2e700e769b0a128cf230bbaaa89f276 Dec 07 18:41:20.242 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-1/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/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:41:20.625 INFO [stdout] a3ed656d27eef9befb2d944d38221129d740a9844a470f36e9b33e2329157631 Dec 07 18:41:20.634 INFO running `"docker" "start" "-a" "a3ed656d27eef9befb2d944d38221129d740a9844a470f36e9b33e2329157631"` Dec 07 18:41:21.827 INFO [stderr] usermod: no changes Dec 07 18:41:21.884 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 07 18:41:21.884 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 07 18:41:21.884 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 18:41:21.884 INFO [stderr] files will be included as a binary target: Dec 07 18:41:21.884 INFO [stderr] Dec 07 18:41:21.884 INFO [stderr] * /source/src/main.rs Dec 07 18:41:21.884 INFO [stderr] Dec 07 18:41:21.884 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 18:41:21.884 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 07 18:41:21.884 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 07 18:41:21.884 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 18:41:21.884 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 18:41:21.884 INFO [stderr] Dec 07 18:41:21.884 INFO [stderr] For more information on this warning you can consult Dec 07 18:41:21.884 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 18:41:21.884 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`, Dec 07 18:41:21.884 INFO [stderr] please set bin.path in Cargo.toml Dec 07 18:41:21.916 INFO [stderr] Compiling dire v0.3.1 (/source) Dec 07 18:41:23.016 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 07 18:41:23.016 INFO [stderr] --> src/unix.rs:21:24 Dec 07 18:41:23.016 INFO [stderr] | Dec 07 18:41:23.016 INFO [stderr] 21 | let home = env::home_dir().ok_or(DirsError::HomeMissing)?; Dec 07 18:41:23.016 INFO [stderr] | ^^^^^^^^^^^^^ Dec 07 18:41:23.016 INFO [stderr] | Dec 07 18:41:23.016 INFO [stderr] = note: #[warn(deprecated)] on by default Dec 07 18:41:23.016 INFO [stderr] Dec 07 18:41:23.528 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.67s Dec 07 18:41:23.532 INFO [stderr] su: No module specific data is present Dec 07 18:41:24.462 INFO running `"docker" "inspect" "a3ed656d27eef9befb2d944d38221129d740a9844a470f36e9b33e2329157631"` Dec 07 18:41:24.698 INFO running `"docker" "rm" "-f" "a3ed656d27eef9befb2d944d38221129d740a9844a470f36e9b33e2329157631"` Dec 07 18:41:25.012 INFO [stdout] a3ed656d27eef9befb2d944d38221129d740a9844a470f36e9b33e2329157631 Dec 07 18:41:25.014 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-1/master#906deae0790bd18681b937fe9a141a3c26cf1855:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/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" "-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:41:25.438 INFO [stdout] 1e5ab9feb00eb7b7c5f4fb7da3eedd39332216c951a24190c6e031d54b5becf0 Dec 07 18:41:25.440 INFO running `"docker" "start" "-a" "1e5ab9feb00eb7b7c5f4fb7da3eedd39332216c951a24190c6e031d54b5becf0"` Dec 07 18:41:27.439 INFO [stderr] usermod: no changes Dec 07 18:41:27.484 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 07 18:41:27.484 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 07 18:41:27.484 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 18:41:27.484 INFO [stderr] files will be included as a binary target: Dec 07 18:41:27.484 INFO [stderr] Dec 07 18:41:27.484 INFO [stderr] * /source/src/main.rs Dec 07 18:41:27.484 INFO [stderr] Dec 07 18:41:27.484 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 18:41:27.484 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 07 18:41:27.484 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 07 18:41:27.484 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 18:41:27.484 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 18:41:27.484 INFO [stderr] Dec 07 18:41:27.484 INFO [stderr] For more information on this warning you can consult Dec 07 18:41:27.484 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 18:41:27.484 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`, Dec 07 18:41:27.484 INFO [stderr] please set bin.path in Cargo.toml Dec 07 18:41:27.504 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.03s Dec 07 18:41:27.508 INFO [stderr] Running /target/debug/deps/dire-b9056f197c33e965 Dec 07 18:41:27.508 INFO [stderr] Running /target/debug/deps/dirs-2212ed3e30cee3a4 Dec 07 18:41:27.508 INFO [stdout] Dec 07 18:41:27.508 INFO [stdout] running 0 tests Dec 07 18:41:27.508 INFO [stdout] Dec 07 18:41:27.508 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 07 18:41:27.508 INFO [stdout] Dec 07 18:41:27.508 INFO [stdout] Dec 07 18:41:27.508 INFO [stdout] running 0 tests Dec 07 18:41:27.508 INFO [stdout] Dec 07 18:41:27.508 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 07 18:41:27.508 INFO [stdout] Dec 07 18:41:27.512 INFO [stderr] Doc-tests dire Dec 07 18:41:28.219 INFO [stdout] Dec 07 18:41:28.219 INFO [stdout] running 0 tests Dec 07 18:41:28.219 INFO [stdout] Dec 07 18:41:28.219 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 07 18:41:28.219 INFO [stdout] Dec 07 18:41:28.226 INFO [stderr] su: No module specific data is present Dec 07 18:41:29.010 INFO running `"docker" "inspect" "1e5ab9feb00eb7b7c5f4fb7da3eedd39332216c951a24190c6e031d54b5becf0"` Dec 07 18:41:29.242 INFO running `"docker" "rm" "-f" "1e5ab9feb00eb7b7c5f4fb7da3eedd39332216c951a24190c6e031d54b5becf0"` Dec 07 18:41:29.561 INFO [stdout] 1e5ab9feb00eb7b7c5f4fb7da3eedd39332216c951a24190c6e031d54b5becf0