Nov 02 22:23:25.834 INFO testing dire-0.3.1 against 1.30.0 for beta-1.31-1
Nov 02 22:23:25.835 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-1/1.30.0:/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 +1.30.0 build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 02 22:23:26.267 INFO blam! 818021809f04480089412707edd04434670245fc9e430644fc68cb9066455845
Nov 02 22:23:26.270 INFO running `"docker" "start" "-a" "818021809f04480089412707edd04434670245fc9e430644fc68cb9066455845"`
Nov 02 22:23:27.681 INFO kablam! usermod: no changes
Nov 02 22:23:27.747 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 22:23:27.747 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 22:23:27.747 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 22:23:27.747 INFO kablam! files will be included as a binary target:
Nov 02 22:23:27.747 INFO kablam! 
Nov 02 22:23:27.747 INFO kablam! * /source/src/main.rs
Nov 02 22:23:27.747 INFO kablam! 
Nov 02 22:23:27.747 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 22:23:27.747 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 22:23:27.747 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 22:23:27.747 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 22:23:27.747 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 22:23:27.747 INFO kablam! 
Nov 02 22:23:27.747 INFO kablam! For more information on this warning you can consult
Nov 02 22:23:27.747 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 22:23:27.747 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 02 22:23:27.747 INFO kablam! please set bin.path in Cargo.toml
Nov 02 22:23:27.779 INFO kablam!    Compiling dire v0.3.1 (/source)
Nov 02 22:23:28.539 INFO kablam! 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 02 22:23:28.539 INFO kablam!   --> src/unix.rs:21:24
Nov 02 22:23:28.539 INFO kablam!    |
Nov 02 22:23:28.539 INFO kablam! 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Nov 02 22:23:28.539 INFO kablam!    |                        ^^^^^^^^^^^^^
Nov 02 22:23:28.539 INFO kablam!    |
Nov 02 22:23:28.539 INFO kablam!    = note: #[warn(deprecated)] on by default
Nov 02 22:23:28.539 INFO kablam! 
Nov 02 22:23:30.040 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.34s
Nov 02 22:23:30.043 INFO kablam! su: No module specific data is present
Nov 02 22:23:31.114 INFO running `"docker" "rm" "-f" "818021809f04480089412707edd04434670245fc9e430644fc68cb9066455845"`
Nov 02 22:23:31.371 INFO blam! 818021809f04480089412707edd04434670245fc9e430644fc68cb9066455845
Nov 02 22:23:31.375 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-1/1.30.0:/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 +1.30.0 test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 02 22:23:31.783 INFO blam! b9316d17274a0cf9c2a976d49ea5e9d37f6a080d4ff7326457851f5dc8cf095d
Nov 02 22:23:31.795 INFO running `"docker" "start" "-a" "b9316d17274a0cf9c2a976d49ea5e9d37f6a080d4ff7326457851f5dc8cf095d"`
Nov 02 22:23:32.968 INFO kablam! usermod: no changes
Nov 02 22:23:33.007 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 22:23:33.007 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 22:23:33.007 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 22:23:33.007 INFO kablam! files will be included as a binary target:
Nov 02 22:23:33.007 INFO kablam! 
Nov 02 22:23:33.007 INFO kablam! * /source/src/main.rs
Nov 02 22:23:33.007 INFO kablam! 
Nov 02 22:23:33.007 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 22:23:33.007 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 22:23:33.007 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 22:23:33.007 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 22:23:33.007 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 22:23:33.007 INFO kablam! 
Nov 02 22:23:33.007 INFO kablam! For more information on this warning you can consult
Nov 02 22:23:33.007 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 22:23:33.007 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 02 22:23:33.007 INFO kablam! please set bin.path in Cargo.toml
Nov 02 22:23:33.027 INFO kablam!    Compiling dire v0.3.1 (/source)
Nov 02 22:23:34.179 INFO kablam! 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 02 22:23:34.180 INFO kablam!   --> src/unix.rs:21:24
Nov 02 22:23:34.180 INFO kablam!    |
Nov 02 22:23:34.180 INFO kablam! 21 |             let home = env::home_dir().ok_or(DirsError::HomeMissing)?;
Nov 02 22:23:34.180 INFO kablam!    |                        ^^^^^^^^^^^^^
Nov 02 22:23:34.180 INFO kablam!    |
Nov 02 22:23:34.180 INFO kablam!    = note: #[warn(deprecated)] on by default
Nov 02 22:23:34.180 INFO kablam! 
Nov 02 22:23:35.265 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.27s
Nov 02 22:23:35.268 INFO kablam! su: No module specific data is present
Nov 02 22:23:35.871 INFO running `"docker" "rm" "-f" "b9316d17274a0cf9c2a976d49ea5e9d37f6a080d4ff7326457851f5dc8cf095d"`
Nov 02 22:23:36.191 INFO blam! b9316d17274a0cf9c2a976d49ea5e9d37f6a080d4ff7326457851f5dc8cf095d
Nov 02 22:23:36.196 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-1/1.30.0:/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 +1.30.0 test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 02 22:23:36.761 INFO blam! 06d3e5186615028b8e60788d5fc732f8b66b7cf1f02ff2447ceabccd8daef051
Nov 02 22:23:36.783 INFO running `"docker" "start" "-a" "06d3e5186615028b8e60788d5fc732f8b66b7cf1f02ff2447ceabccd8daef051"`
Nov 02 22:23:37.955 INFO kablam! usermod: no changes
Nov 02 22:23:38.030 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 22:23:38.030 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 22:23:38.030 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 22:23:38.030 INFO kablam! files will be included as a binary target:
Nov 02 22:23:38.030 INFO kablam! 
Nov 02 22:23:38.030 INFO kablam! * /source/src/main.rs
Nov 02 22:23:38.030 INFO kablam! 
Nov 02 22:23:38.031 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 22:23:38.031 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 22:23:38.031 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 22:23:38.031 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 22:23:38.031 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 22:23:38.031 INFO kablam! 
Nov 02 22:23:38.031 INFO kablam! For more information on this warning you can consult
Nov 02 22:23:38.031 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 22:23:38.031 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`,
Nov 02 22:23:38.031 INFO kablam! please set bin.path in Cargo.toml
Nov 02 22:23:38.031 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.04s
Nov 02 22:23:38.031 INFO kablam!      Running /target/debug/deps/dire-cc69829a45702e2e
Nov 02 22:23:38.039 INFO kablam!      Running /target/debug/deps/dirs-a4b1bf3f39587a3f
Nov 02 22:23:38.039 INFO blam! 
Nov 02 22:23:38.039 INFO blam! running 0 tests
Nov 02 22:23:38.039 INFO blam! 
Nov 02 22:23:38.039 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 22:23:38.039 INFO blam! 
Nov 02 22:23:38.039 INFO blam! 
Nov 02 22:23:38.039 INFO blam! running 0 tests
Nov 02 22:23:38.039 INFO blam! 
Nov 02 22:23:38.039 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 22:23:38.039 INFO blam! 
Nov 02 22:23:38.041 INFO kablam!    Doc-tests dire
Nov 02 22:23:39.287 INFO blam! 
Nov 02 22:23:39.287 INFO blam! running 0 tests
Nov 02 22:23:39.288 INFO blam! 
Nov 02 22:23:39.288 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 22:23:39.288 INFO blam! 
Nov 02 22:23:39.295 INFO kablam! su: No module specific data is present
Nov 02 22:23:40.315 INFO running `"docker" "rm" "-f" "06d3e5186615028b8e60788d5fc732f8b66b7cf1f02ff2447ceabccd8daef051"`
Nov 02 22:23:40.667 INFO blam! 06d3e5186615028b8e60788d5fc732f8b66b7cf1f02ff2447ceabccd8daef051
