Nov 18 16:02:18.745 INFO testing dire-0.3.1 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 16:02:18.747 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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.271 INFO [stdout] 8a35b139f086ca8a0b269beebe05cc53b885a9cf912d3dc9dbbbabcfde450b6e
Nov 18 16:02:19.275 INFO running `"docker" "start" "-a" "8a35b139f086ca8a0b269beebe05cc53b885a9cf912d3dc9dbbbabcfde450b6e"`
Nov 18 16:02:20.736 INFO [stderr] usermod: no changes
Nov 18 16:02:20.815 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 16:02:20.815 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 16:02:20.815 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 16:02:20.815 INFO [stderr] files will be included as a binary target:
Nov 18 16:02:20.815 INFO [stderr] 
Nov 18 16:02:20.815 INFO [stderr] * /source/src/main.rs
Nov 18 16:02:20.815 INFO [stderr] 
Nov 18 16:02:20.815 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 16:02:20.815 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 16:02:20.815 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 16:02:20.815 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 16:02:20.815 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 16:02:20.815 INFO [stderr] 
Nov 18 16:02:20.815 INFO [stderr] For more information on this warning you can consult
Nov 18 16:02:20.815 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 16:02:20.815 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 18 16:02:20.815 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 16:02:20.839 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.976 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.21s
Nov 18 16:02:22.980 INFO [stderr] su: No module specific data is present
Nov 18 16:02:23.613 INFO running `"docker" "inspect" "8a35b139f086ca8a0b269beebe05cc53b885a9cf912d3dc9dbbbabcfde450b6e"`
Nov 18 16:02:23.999 INFO running `"docker" "rm" "-f" "8a35b139f086ca8a0b269beebe05cc53b885a9cf912d3dc9dbbbabcfde450b6e"`
Nov 18 16:02:24.403 INFO [stdout] 8a35b139f086ca8a0b269beebe05cc53b885a9cf912d3dc9dbbbabcfde450b6e
Nov 18 16:02:24.405 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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:25.020 INFO [stdout] 3177e1fd826191e303e38355785156272cfc0ff49f3110788660243f012cae68
Nov 18 16:02:25.021 INFO running `"docker" "start" "-a" "3177e1fd826191e303e38355785156272cfc0ff49f3110788660243f012cae68"`
Nov 18 16:02:26.203 INFO [stderr] usermod: no changes
Nov 18 16:02:26.271 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 16:02:26.271 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 16:02:26.271 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 16:02:26.271 INFO [stderr] files will be included as a binary target:
Nov 18 16:02:26.271 INFO [stderr] 
Nov 18 16:02:26.271 INFO [stderr] * /source/src/main.rs
Nov 18 16:02:26.271 INFO [stderr] 
Nov 18 16:02:26.271 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 16:02:26.271 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 16:02:26.271 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 16:02:26.271 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 16:02:26.271 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 16:02:26.271 INFO [stderr] 
Nov 18 16:02:26.271 INFO [stderr] For more information on this warning you can consult
Nov 18 16:02:26.271 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 16:02:26.271 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 18 16:02:26.271 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 16:02:26.291 INFO [stderr]    Compiling dire v0.3.1 (/source)
Nov 18 16:02:27.135 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.135 INFO [stderr]   --> src/unix.rs:21:24
Nov 18 16:02:27.135 INFO [stderr]    |
Nov 18 16:02:27.135 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Nov 18 16:02:27.135 INFO [stderr]    |                        ^^^^^^^^^^^^^
Nov 18 16:02:27.135 INFO [stderr]    |
Nov 18 16:02:27.135 INFO [stderr]    = note: #[warn(deprecated)] on by default
Nov 18 16:02:27.135 INFO [stderr] 
Nov 18 16:02:27.863 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.63s
Nov 18 16:02:27.867 INFO [stderr] su: No module specific data is present
Nov 18 16:02:28.673 INFO running `"docker" "inspect" "3177e1fd826191e303e38355785156272cfc0ff49f3110788660243f012cae68"`
Nov 18 16:02:29.041 INFO running `"docker" "rm" "-f" "3177e1fd826191e303e38355785156272cfc0ff49f3110788660243f012cae68"`
Nov 18 16:02:29.347 INFO [stdout] 3177e1fd826191e303e38355785156272cfc0ff49f3110788660243f012cae68
Nov 18 16:02:29.352 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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.859 INFO [stdout] 7f8974c0c26eb9a0d1fdc2577a5835459f861b77f99ee55d2ac907f2533eb7eb
Nov 18 16:02:29.872 INFO running `"docker" "start" "-a" "7f8974c0c26eb9a0d1fdc2577a5835459f861b77f99ee55d2ac907f2533eb7eb"`
Nov 18 16:02:31.010 INFO [stderr] usermod: no changes
Nov 18 16:02:31.087 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 16:02:31.087 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 16:02:31.087 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 16:02:31.087 INFO [stderr] files will be included as a binary target:
Nov 18 16:02:31.087 INFO [stderr] 
Nov 18 16:02:31.087 INFO [stderr] * /source/src/main.rs
Nov 18 16:02:31.087 INFO [stderr] 
Nov 18 16:02:31.087 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 16:02:31.087 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 16:02:31.087 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 16:02:31.087 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 16:02:31.087 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 16:02:31.087 INFO [stderr] 
Nov 18 16:02:31.087 INFO [stderr] For more information on this warning you can consult
Nov 18 16:02:31.087 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 16:02:31.087 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 18 16:02:31.087 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 16:02:31.107 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.05s
Nov 18 16:02:31.107 INFO [stdout] 
Nov 18 16:02:31.107 INFO [stdout] running 0 tests
Nov 18 16:02:31.107 INFO [stdout] 
Nov 18 16:02:31.107 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 16:02:31.107 INFO [stdout] 
Nov 18 16:02:31.107 INFO [stdout] 
Nov 18 16:02:31.107 INFO [stderr]      Running /target/debug/deps/dire-09af5a0b31434bd9
Nov 18 16:02:31.107 INFO [stdout] running 0 tests
Nov 18 16:02:31.107 INFO [stderr]      Running /target/debug/deps/dirs-54404fee353a6aa9
Nov 18 16:02:31.107 INFO [stdout] 
Nov 18 16:02:31.107 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 16:02:31.107 INFO [stdout] 
Nov 18 16:02:31.115 INFO [stderr]    Doc-tests dire
Nov 18 16:02:31.847 INFO [stdout] 
Nov 18 16:02:31.847 INFO [stdout] running 0 tests
Nov 18 16:02:31.847 INFO [stdout] 
Nov 18 16:02:31.847 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 16:02:31.847 INFO [stdout] 
Nov 18 16:02:31.855 INFO [stderr] su: No module specific data is present
Nov 18 16:02:32.402 INFO running `"docker" "inspect" "7f8974c0c26eb9a0d1fdc2577a5835459f861b77f99ee55d2ac907f2533eb7eb"`
Nov 18 16:02:32.817 INFO running `"docker" "rm" "-f" "7f8974c0c26eb9a0d1fdc2577a5835459f861b77f99ee55d2ac907f2533eb7eb"`
Nov 18 16:02:33.153 INFO [stdout] 7f8974c0c26eb9a0d1fdc2577a5835459f861b77f99ee55d2ac907f2533eb7eb