Dec 07 18:41:15.229 INFO testing dire-0.3.1 against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514
Dec 07 18:41:15.229 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-3/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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:15.549 INFO [stdout] 36110f8066f12981ed3026b2bde4a5ed28c1e1277a3148c8e113e8b20b85760d
Dec 07 18:41:15.550 INFO running `"docker" "start" "-a" "36110f8066f12981ed3026b2bde4a5ed28c1e1277a3148c8e113e8b20b85760d"`
Dec 07 18:41:16.608 INFO [stderr] usermod: no changes
Dec 07 18:41:16.656 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 07 18:41:16.656 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 07 18:41:16.656 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 07 18:41:16.656 INFO [stderr] files will be included as a binary target:
Dec 07 18:41:16.656 INFO [stderr] 
Dec 07 18:41:16.656 INFO [stderr] * /source/src/main.rs
Dec 07 18:41:16.656 INFO [stderr] 
Dec 07 18:41:16.656 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 07 18:41:16.656 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 07 18:41:16.656 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 07 18:41:16.656 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 07 18:41:16.656 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 07 18:41:16.656 INFO [stderr] 
Dec 07 18:41:16.656 INFO [stderr] For more information on this warning you can consult
Dec 07 18:41:16.656 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 07 18:41:16.656 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 07 18:41:16.656 INFO [stderr] please set bin.path in Cargo.toml
Dec 07 18:41:16.668 INFO [stderr]    Compiling dire v0.3.1 (/source)
Dec 07 18:41:17.197 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.197 INFO [stderr]   --> src/unix.rs:21:24
Dec 07 18:41:17.197 INFO [stderr]    |
Dec 07 18:41:17.197 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Dec 07 18:41:17.197 INFO [stderr]    |                        ^^^^^^^^^^^^^
Dec 07 18:41:17.197 INFO [stderr]    |
Dec 07 18:41:17.197 INFO [stderr]    = note: #[warn(deprecated)] on by default
Dec 07 18:41:17.197 INFO [stderr] 
Dec 07 18:41:18.625 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.99s
Dec 07 18:41:18.632 INFO [stderr] su: No module specific data is present
Dec 07 18:41:19.591 INFO running `"docker" "inspect" "36110f8066f12981ed3026b2bde4a5ed28c1e1277a3148c8e113e8b20b85760d"`
Dec 07 18:41:19.841 INFO running `"docker" "rm" "-f" "36110f8066f12981ed3026b2bde4a5ed28c1e1277a3148c8e113e8b20b85760d"`
Dec 07 18:41:20.111 INFO [stdout] 36110f8066f12981ed3026b2bde4a5ed28c1e1277a3148c8e113e8b20b85760d
Dec 07 18:41:20.208 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-3/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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.652 INFO [stdout] 9af436f67931ddbb52c9d291b9dbf77cdca6ee484296bfa624fa5fc140352fec
Dec 07 18:41:20.658 INFO running `"docker" "start" "-a" "9af436f67931ddbb52c9d291b9dbf77cdca6ee484296bfa624fa5fc140352fec"`
Dec 07 18:41:21.888 INFO [stderr] usermod: no changes
Dec 07 18:41:21.928 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 07 18:41:21.928 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 07 18:41:21.928 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 07 18:41:21.928 INFO [stderr] files will be included as a binary target:
Dec 07 18:41:21.928 INFO [stderr] 
Dec 07 18:41:21.928 INFO [stderr] * /source/src/main.rs
Dec 07 18:41:21.928 INFO [stderr] 
Dec 07 18:41:21.928 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 07 18:41:21.928 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 07 18:41:21.928 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 07 18:41:21.928 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 07 18:41:21.928 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 07 18:41:21.928 INFO [stderr] 
Dec 07 18:41:21.928 INFO [stderr] For more information on this warning you can consult
Dec 07 18:41:21.928 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 07 18:41:21.928 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 07 18:41:21.928 INFO [stderr] please set bin.path in Cargo.toml
Dec 07 18:41:21.968 INFO [stderr]    Compiling dire v0.3.1 (/source)
Dec 07 18:41:23.044 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.044 INFO [stderr]   --> src/unix.rs:21:24
Dec 07 18:41:23.044 INFO [stderr]    |
Dec 07 18:41:23.044 INFO [stderr] 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Dec 07 18:41:23.044 INFO [stderr]    |                        ^^^^^^^^^^^^^
Dec 07 18:41:23.044 INFO [stderr]    |
Dec 07 18:41:23.044 INFO [stderr]    = note: #[warn(deprecated)] on by default
Dec 07 18:41:23.044 INFO [stderr] 
Dec 07 18:41:23.520 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.61s
Dec 07 18:41:23.524 INFO [stderr] su: No module specific data is present
Dec 07 18:41:24.368 INFO running `"docker" "inspect" "9af436f67931ddbb52c9d291b9dbf77cdca6ee484296bfa624fa5fc140352fec"`
Dec 07 18:41:24.648 INFO running `"docker" "rm" "-f" "9af436f67931ddbb52c9d291b9dbf77cdca6ee484296bfa624fa5fc140352fec"`
Dec 07 18:41:25.001 INFO [stdout] 9af436f67931ddbb52c9d291b9dbf77cdca6ee484296bfa624fa5fc140352fec
Dec 07 18:41:25.007 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-3/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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.500 INFO [stdout] e5b00519c27410682f84b373568070fe1e325ea3f70ca1c9909572d2230daa9f
Dec 07 18:41:25.504 INFO running `"docker" "start" "-a" "e5b00519c27410682f84b373568070fe1e325ea3f70ca1c9909572d2230daa9f"`
Dec 07 18:41:27.005 INFO [stderr] usermod: no changes
Dec 07 18:41:27.088 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 07 18:41:27.088 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 07 18:41:27.088 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 07 18:41:27.088 INFO [stderr] files will be included as a binary target:
Dec 07 18:41:27.088 INFO [stderr] 
Dec 07 18:41:27.088 INFO [stderr] * /source/src/main.rs
Dec 07 18:41:27.088 INFO [stderr] 
Dec 07 18:41:27.088 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 07 18:41:27.088 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 07 18:41:27.088 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 07 18:41:27.088 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 07 18:41:27.088 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 07 18:41:27.088 INFO [stderr] 
Dec 07 18:41:27.088 INFO [stderr] For more information on this warning you can consult
Dec 07 18:41:27.088 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 07 18:41:27.088 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Dec 07 18:41:27.088 INFO [stderr] please set bin.path in Cargo.toml
Dec 07 18:41:27.112 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.07s
Dec 07 18:41:27.120 INFO [stderr]      Running /target/debug/deps/dire-d2b4b1ef044b2f8f
Dec 07 18:41:27.125 INFO [stdout] 
Dec 07 18:41:27.125 INFO [stdout] running 0 tests
Dec 07 18:41:27.125 INFO [stdout] 
Dec 07 18:41:27.125 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 07 18:41:27.125 INFO [stdout] 
Dec 07 18:41:27.128 INFO [stdout] 
Dec 07 18:41:27.128 INFO [stderr]      Running /target/debug/deps/dirs-7eb98447dd5c13ef
Dec 07 18:41:27.128 INFO [stdout] running 0 tests
Dec 07 18:41:27.128 INFO [stderr]    Doc-tests dire
Dec 07 18:41:27.128 INFO [stdout] 
Dec 07 18:41:27.128 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 07 18:41:27.128 INFO [stdout] 
Dec 07 18:41:28.079 INFO [stdout] 
Dec 07 18:41:28.079 INFO [stdout] running 0 tests
Dec 07 18:41:28.079 INFO [stdout] 
Dec 07 18:41:28.079 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 07 18:41:28.079 INFO [stdout] 
Dec 07 18:41:28.086 INFO [stderr] su: No module specific data is present
Dec 07 18:41:28.870 INFO running `"docker" "inspect" "e5b00519c27410682f84b373568070fe1e325ea3f70ca1c9909572d2230daa9f"`
Dec 07 18:41:29.173 INFO running `"docker" "rm" "-f" "e5b00519c27410682f84b373568070fe1e325ea3f70ca1c9909572d2230daa9f"`
Dec 07 18:41:29.561 INFO [stdout] e5b00519c27410682f84b373568070fe1e325ea3f70ca1c9909572d2230daa9f