Nov 18 16:02:19.079 INFO testing dire-0.3.1 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 16:02:19.079 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-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"`
Nov 18 16:02:19.504 INFO [stdout] 59c33de67d45e3cab669bff27526661f3684ea0a42328443c1dd9e0351c2fede
Nov 18 16:02:19.509 INFO running `"docker" "start" "-a" "59c33de67d45e3cab669bff27526661f3684ea0a42328443c1dd9e0351c2fede"`
Nov 18 16:02:20.771 INFO [stderr] usermod: no changes
Nov 18 16:02:20.835 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 16:02:20.835 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 16:02:20.835 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 16:02:20.835 INFO [stderr] files will be included as a binary target:
Nov 18 16:02:20.835 INFO [stderr] 
Nov 18 16:02:20.835 INFO [stderr] * /source/src/main.rs
Nov 18 16:02:20.835 INFO [stderr] 
Nov 18 16:02:20.835 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 16:02:20.835 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 16:02:20.835 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 16:02:20.835 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 16:02:20.835 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 16:02:20.835 INFO [stderr] 
Nov 18 16:02:20.835 INFO [stderr] For more information on this warning you can consult
Nov 18 16:02:20.835 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 16:02:20.835 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 18 16:02:20.835 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 16:02:20.852 INFO [stderr]    Compiling dire v0.3.1 (/source)
Nov 18 16:02:21.407 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 18 16:02:21.407 INFO [stderr]   --> src/unix.rs:21:24
Nov 18 16:02:21.407 INFO [stderr]    |
Nov 18 16:02:21.407 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Nov 18 16:02:21.407 INFO [stderr]    |                        ^^^^^^^^^^^^^
Nov 18 16:02:21.407 INFO [stderr]    |
Nov 18 16:02:21.407 INFO [stderr]    = note: #[warn(deprecated)] on by default
Nov 18 16:02:21.407 INFO [stderr] 
Nov 18 16:02:22.827 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.03s
Nov 18 16:02:22.832 INFO [stderr] su: No module specific data is present
Nov 18 16:02:23.681 INFO running `"docker" "inspect" "59c33de67d45e3cab669bff27526661f3684ea0a42328443c1dd9e0351c2fede"`
Nov 18 16:02:23.975 INFO running `"docker" "rm" "-f" "59c33de67d45e3cab669bff27526661f3684ea0a42328443c1dd9e0351c2fede"`
Nov 18 16:02:24.253 INFO [stdout] 59c33de67d45e3cab669bff27526661f3684ea0a42328443c1dd9e0351c2fede
Nov 18 16:02:24.259 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-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"`
Nov 18 16:02:24.962 INFO [stdout] bc825895ad5d00a3c389023f582f94f92f3f3896e2c9011a5bfcfb6d0a6fe6d2
Nov 18 16:02:24.962 INFO running `"docker" "start" "-a" "bc825895ad5d00a3c389023f582f94f92f3f3896e2c9011a5bfcfb6d0a6fe6d2"`
Nov 18 16:02:26.127 INFO [stderr] usermod: no changes
Nov 18 16:02:26.175 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 16:02:26.175 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 16:02:26.175 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 16:02:26.175 INFO [stderr] files will be included as a binary target:
Nov 18 16:02:26.176 INFO [stderr] 
Nov 18 16:02:26.176 INFO [stderr] * /source/src/main.rs
Nov 18 16:02:26.176 INFO [stderr] 
Nov 18 16:02:26.176 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 16:02:26.176 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 16:02:26.176 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 16:02:26.176 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 16:02:26.176 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 16:02:26.176 INFO [stderr] 
Nov 18 16:02:26.176 INFO [stderr] For more information on this warning you can consult
Nov 18 16:02:26.176 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 16:02:26.176 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 18 16:02:26.176 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 16:02:26.210 INFO [stderr]    Compiling dire v0.3.1 (/source)
Nov 18 16:02:27.263 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 18 16:02:27.263 INFO [stderr]   --> src/unix.rs:21:24
Nov 18 16:02:27.263 INFO [stderr]    |
Nov 18 16:02:27.263 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Nov 18 16:02:27.263 INFO [stderr]    |                        ^^^^^^^^^^^^^
Nov 18 16:02:27.263 INFO [stderr]    |
Nov 18 16:02:27.263 INFO [stderr]    = note: #[warn(deprecated)] on by default
Nov 18 16:02:27.263 INFO [stderr] 
Nov 18 16:02:27.883 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.72s
Nov 18 16:02:27.887 INFO [stderr] su: No module specific data is present
Nov 18 16:02:28.651 INFO running `"docker" "inspect" "bc825895ad5d00a3c389023f582f94f92f3f3896e2c9011a5bfcfb6d0a6fe6d2"`
Nov 18 16:02:28.951 INFO running `"docker" "rm" "-f" "bc825895ad5d00a3c389023f582f94f92f3f3896e2c9011a5bfcfb6d0a6fe6d2"`
Nov 18 16:02:29.319 INFO [stdout] bc825895ad5d00a3c389023f582f94f92f3f3896e2c9011a5bfcfb6d0a6fe6d2
Nov 18 16:02:29.326 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-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"`
Nov 18 16:02:29.811 INFO [stdout] b57e105ae862ccc943cf3bba305a9110b2a2f7392486215e56a556f5bc1eddfe
Nov 18 16:02:29.817 INFO running `"docker" "start" "-a" "b57e105ae862ccc943cf3bba305a9110b2a2f7392486215e56a556f5bc1eddfe"`
Nov 18 16:02:30.887 INFO [stderr] usermod: no changes
Nov 18 16:02:30.947 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 16:02:30.947 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 16:02:30.947 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 16:02:30.947 INFO [stderr] files will be included as a binary target:
Nov 18 16:02:30.947 INFO [stderr] 
Nov 18 16:02:30.947 INFO [stderr] * /source/src/main.rs
Nov 18 16:02:30.947 INFO [stderr] 
Nov 18 16:02:30.947 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 16:02:30.947 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 16:02:30.947 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 16:02:30.947 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 16:02:30.947 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 16:02:30.947 INFO [stderr] 
Nov 18 16:02:30.947 INFO [stderr] For more information on this warning you can consult
Nov 18 16:02:30.947 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 16:02:30.947 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 18 16:02:30.947 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 16:02:30.954 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.03s
Nov 18 16:02:30.956 INFO [stderr]      Running /target/debug/deps/dire-27f64507f7bae837
Nov 18 16:02:30.956 INFO [stdout] 
Nov 18 16:02:30.956 INFO [stdout] running 0 tests
Nov 18 16:02:30.956 INFO [stdout] 
Nov 18 16:02:30.956 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 16:02:30.956 INFO [stdout] 
Nov 18 16:02:30.963 INFO [stdout] 
Nov 18 16:02:30.963 INFO [stderr]      Running /target/debug/deps/dirs-04ff716ec5832917
Nov 18 16:02:30.963 INFO [stdout] running 0 tests
Nov 18 16:02:30.963 INFO [stdout] 
Nov 18 16:02:30.963 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 16:02:30.963 INFO [stdout] 
Nov 18 16:02:30.970 INFO [stderr]    Doc-tests dire
Nov 18 16:02:31.905 INFO [stdout] 
Nov 18 16:02:31.905 INFO [stdout] running 0 tests
Nov 18 16:02:31.905 INFO [stdout] 
Nov 18 16:02:31.905 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 16:02:31.905 INFO [stdout] 
Nov 18 16:02:31.915 INFO [stderr] su: No module specific data is present
Nov 18 16:02:32.483 INFO running `"docker" "inspect" "b57e105ae862ccc943cf3bba305a9110b2a2f7392486215e56a556f5bc1eddfe"`
Nov 18 16:02:32.782 INFO running `"docker" "rm" "-f" "b57e105ae862ccc943cf3bba305a9110b2a2f7392486215e56a556f5bc1eddfe"`
Nov 18 16:02:33.071 INFO [stdout] b57e105ae862ccc943cf3bba305a9110b2a2f7392486215e56a556f5bc1eddfe