Nov 05 00:43:23.587 INFO checking dire-0.3.1 against try#e740b9aa0b624fa39feb39613e76d15bdf57e594 for pr-55655 Nov 05 00:43:23.587 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55655/worker-2/try#e740b9aa0b624fa39feb39613e76d15bdf57e594:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-55655/try#e740b9aa0b624fa39feb39613e76d15bdf57e594:/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 +e740b9aa0b624fa39feb39613e76d15bdf57e594-alt check --frozen --all --all-targets" "-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 05 00:43:24.160 INFO blam! ff1de587c62819c302577ef4e1cbcf18408b951240cc6cbfa33f48cf02e91a46 Nov 05 00:43:24.163 INFO running `"docker" "start" "-a" "ff1de587c62819c302577ef4e1cbcf18408b951240cc6cbfa33f48cf02e91a46"` Nov 05 00:43:25.552 INFO kablam! usermod: no changes Nov 05 00:43:25.595 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 05 00:43:25.595 INFO kablam! disables Cargo from automatically inferring other binary targets. Nov 05 00:43:25.595 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Nov 05 00:43:25.595 INFO kablam! files will be included as a binary target: Nov 05 00:43:25.595 INFO kablam! Nov 05 00:43:25.595 INFO kablam! * /source/src/main.rs Nov 05 00:43:25.595 INFO kablam! Nov 05 00:43:25.595 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Nov 05 00:43:25.595 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself Nov 05 00:43:25.595 INFO kablam! and disable this warning by adding `autobins = false` to your [package] Nov 05 00:43:25.595 INFO kablam! section. You may also move the files to a location where Cargo would not Nov 05 00:43:25.595 INFO kablam! automatically infer them to be a target, such as in subfolders. Nov 05 00:43:25.595 INFO kablam! Nov 05 00:43:25.595 INFO kablam! For more information on this warning you can consult Nov 05 00:43:25.595 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Nov 05 00:43:25.595 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dirs`, Nov 05 00:43:25.595 INFO kablam! please set bin.path in Cargo.toml Nov 05 00:43:25.604 INFO kablam! Checking dire v0.3.1 (/source) Nov 05 00:43:26.455 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 05 00:43:26.455 INFO kablam! --> src/unix.rs:21:24 Nov 05 00:43:26.455 INFO kablam! | Nov 05 00:43:26.455 INFO kablam! 21 | let home = env::home_dir().ok_or(DirsError::HomeMissing)?; Nov 05 00:43:26.455 INFO kablam! | ^^^^^^^^^^^^^ Nov 05 00:43:26.455 INFO kablam! | Nov 05 00:43:26.455 INFO kablam! = note: #[warn(deprecated)] on by default Nov 05 00:43:26.455 INFO kablam! Nov 05 00:43:26.967 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 05 00:43:26.967 INFO kablam! --> src/unix.rs:21:24 Nov 05 00:43:26.967 INFO kablam! | Nov 05 00:43:26.967 INFO kablam! 21 | let home = env::home_dir().ok_or(DirsError::HomeMissing)?; Nov 05 00:43:26.967 INFO kablam! | ^^^^^^^^^^^^^ Nov 05 00:43:26.967 INFO kablam! | Nov 05 00:43:26.967 INFO kablam! = note: #[warn(deprecated)] on by default Nov 05 00:43:26.967 INFO kablam! Nov 05 00:43:27.773 INFO kablam! Finished dev [unoptimized + debuginfo] target(s) in 2.19s Nov 05 00:43:27.774 INFO kablam! su: No module specific data is present Nov 05 00:43:28.301 INFO running `"docker" "rm" "-f" "ff1de587c62819c302577ef4e1cbcf18408b951240cc6cbfa33f48cf02e91a46"` Nov 05 00:43:28.603 INFO blam! ff1de587c62819c302577ef4e1cbcf18408b951240cc6cbfa33f48cf02e91a46