Dec 15 16:56:05.180 INFO testing dire-0.3.1 against try#aa49d8ef14939ddec0e34b346b60174a5673d48f for pr-56550
Dec 15 16:56:05.180 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-3/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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:05.648 INFO [stdout] 699680cd1ae5d2f3a8445c7059f12f550fb51f5ec847c76f081f108b911a967d
Dec 15 16:56:05.650 INFO running `"docker" "start" "-a" "699680cd1ae5d2f3a8445c7059f12f550fb51f5ec847c76f081f108b911a967d"`
Dec 15 16:56:07.575 INFO [stderr] usermod: no changes
Dec 15 16:56:07.616 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 15 16:56:07.616 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 15 16:56:07.616 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 15 16:56:07.616 INFO [stderr] files will be included as a binary target:
Dec 15 16:56:07.616 INFO [stderr] 
Dec 15 16:56:07.616 INFO [stderr] * /source/src/main.rs
Dec 15 16:56:07.616 INFO [stderr] 
Dec 15 16:56:07.616 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 15 16:56:07.616 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 15 16:56:07.616 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 15 16:56:07.616 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 15 16:56:07.616 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 15 16:56:07.616 INFO [stderr] 
Dec 15 16:56:07.616 INFO [stderr] For more information on this warning you can consult
Dec 15 16:56:07.616 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 15 16:56:07.616 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 15 16:56:07.616 INFO [stderr] please set bin.path in Cargo.toml
Dec 15 16:56:07.623 INFO [stderr]    Compiling dire v0.3.1 (/source)
Dec 15 16:56:08.315 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:08.315 INFO [stderr]   --> src/unix.rs:21:24
Dec 15 16:56:08.315 INFO [stderr]    |
Dec 15 16:56:08.315 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Dec 15 16:56:08.315 INFO [stderr]    |                        ^^^^^^^^^^^^^
Dec 15 16:56:08.315 INFO [stderr]    |
Dec 15 16:56:08.315 INFO [stderr]    = note: #[warn(deprecated)] on by default
Dec 15 16:56:08.315 INFO [stderr] 
Dec 15 16:56:10.056 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.46s
Dec 15 16:56:10.063 INFO [stderr] su: No module specific data is present
Dec 15 16:56:10.979 INFO running `"docker" "inspect" "699680cd1ae5d2f3a8445c7059f12f550fb51f5ec847c76f081f108b911a967d"`
Dec 15 16:56:11.213 INFO running `"docker" "rm" "-f" "699680cd1ae5d2f3a8445c7059f12f550fb51f5ec847c76f081f108b911a967d"`
Dec 15 16:56:11.536 INFO [stdout] 699680cd1ae5d2f3a8445c7059f12f550fb51f5ec847c76f081f108b911a967d
Dec 15 16:56:11.541 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-3/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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:12.056 INFO [stdout] 61c18bf2a4cef5eaaceac602893e850562e54cec2d695a98b00bfdb4429e57c6
Dec 15 16:56:12.060 INFO running `"docker" "start" "-a" "61c18bf2a4cef5eaaceac602893e850562e54cec2d695a98b00bfdb4429e57c6"`
Dec 15 16:56:13.431 INFO [stderr] usermod: no changes
Dec 15 16:56:13.479 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 15 16:56:13.479 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 15 16:56:13.479 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 15 16:56:13.479 INFO [stderr] files will be included as a binary target:
Dec 15 16:56:13.479 INFO [stderr] 
Dec 15 16:56:13.479 INFO [stderr] * /source/src/main.rs
Dec 15 16:56:13.479 INFO [stderr] 
Dec 15 16:56:13.479 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 15 16:56:13.479 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 15 16:56:13.479 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 15 16:56:13.479 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 15 16:56:13.479 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 15 16:56:13.479 INFO [stderr] 
Dec 15 16:56:13.479 INFO [stderr] For more information on this warning you can consult
Dec 15 16:56:13.479 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 15 16:56:13.479 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 15 16:56:13.479 INFO [stderr] please set bin.path in Cargo.toml
Dec 15 16:56:13.489 INFO [stderr]    Compiling dire v0.3.1 (/source)
Dec 15 16:56:14.451 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:14.451 INFO [stderr]   --> src/unix.rs:21:24
Dec 15 16:56:14.451 INFO [stderr]    |
Dec 15 16:56:14.451 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Dec 15 16:56:14.451 INFO [stderr]    |                        ^^^^^^^^^^^^^
Dec 15 16:56:14.451 INFO [stderr]    |
Dec 15 16:56:14.451 INFO [stderr]    = note: #[warn(deprecated)] on by default
Dec 15 16:56:14.451 INFO [stderr] 
Dec 15 16:56:15.026 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.56s
Dec 15 16:56:15.030 INFO [stderr] su: No module specific data is present
Dec 15 16:56:15.843 INFO running `"docker" "inspect" "61c18bf2a4cef5eaaceac602893e850562e54cec2d695a98b00bfdb4429e57c6"`
Dec 15 16:56:16.143 INFO running `"docker" "rm" "-f" "61c18bf2a4cef5eaaceac602893e850562e54cec2d695a98b00bfdb4429e57c6"`
Dec 15 16:56:16.375 INFO [stdout] 61c18bf2a4cef5eaaceac602893e850562e54cec2d695a98b00bfdb4429e57c6
Dec 15 16:56:16.380 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-3/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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:16.855 INFO [stdout] 9000f92b3f50e077e4296857af40917e7593454dd0f65e6938c1b9c709d60ec2
Dec 15 16:56:16.863 INFO running `"docker" "start" "-a" "9000f92b3f50e077e4296857af40917e7593454dd0f65e6938c1b9c709d60ec2"`
Dec 15 16:56:18.008 INFO [stderr] usermod: no changes
Dec 15 16:56:18.063 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 15 16:56:18.063 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 15 16:56:18.063 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 15 16:56:18.063 INFO [stderr] files will be included as a binary target:
Dec 15 16:56:18.063 INFO [stderr] 
Dec 15 16:56:18.063 INFO [stderr] * /source/src/main.rs
Dec 15 16:56:18.063 INFO [stderr] 
Dec 15 16:56:18.063 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 15 16:56:18.063 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 15 16:56:18.063 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 15 16:56:18.063 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 15 16:56:18.063 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 15 16:56:18.063 INFO [stderr] 
Dec 15 16:56:18.063 INFO [stderr] For more information on this warning you can consult
Dec 15 16:56:18.063 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 15 16:56:18.063 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 15 16:56:18.063 INFO [stderr] please set bin.path in Cargo.toml
Dec 15 16:56:18.078 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.04s
Dec 15 16:56:18.087 INFO [stderr]      Running /target/debug/deps/dire-d98294ed51255468
Dec 15 16:56:18.091 INFO [stdout] 
Dec 15 16:56:18.091 INFO [stdout] running 0 tests
Dec 15 16:56:18.091 INFO [stdout] 
Dec 15 16:56:18.091 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 15 16:56:18.091 INFO [stdout] 
Dec 15 16:56:18.095 INFO [stderr]      Running /target/debug/deps/dirs-4ca128048368587d
Dec 15 16:56:18.103 INFO [stderr]    Doc-tests dire
Dec 15 16:56:18.103 INFO [stdout] 
Dec 15 16:56:18.103 INFO [stdout] running 0 tests
Dec 15 16:56:18.103 INFO [stdout] 
Dec 15 16:56:18.103 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 15 16:56:18.103 INFO [stdout] 
Dec 15 16:56:19.235 INFO [stdout] 
Dec 15 16:56:19.235 INFO [stdout] running 0 tests
Dec 15 16:56:19.235 INFO [stdout] 
Dec 15 16:56:19.235 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 15 16:56:19.235 INFO [stdout] 
Dec 15 16:56:19.243 INFO [stderr] su: No module specific data is present
Dec 15 16:56:19.935 INFO running `"docker" "inspect" "9000f92b3f50e077e4296857af40917e7593454dd0f65e6938c1b9c709d60ec2"`
Dec 15 16:56:20.209 INFO running `"docker" "rm" "-f" "9000f92b3f50e077e4296857af40917e7593454dd0f65e6938c1b9c709d60ec2"`
Dec 15 16:56:20.515 INFO [stdout] 9000f92b3f50e077e4296857af40917e7593454dd0f65e6938c1b9c709d60ec2