Dec 14 19:59:22.697 INFO testing sherpa-0.4.0 against master#bd47d6825bf4090517549d33cfef10d3300b4a75 for pr-56550 Dec 14 19:59:22.697 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-1/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-56550/master#bd47d6825bf4090517549d33cfef10d3300b4a75:/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 +bd47d6825bf4090517549d33cfef10d3300b4a75-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 14 19:59:22.857 INFO [stdout] f1a395bdc0457e70e9e12e8e6d7b25d1bdbf169802d745687dd5bfe07bf9ca37 Dec 14 19:59:22.860 INFO running `"docker" "start" "-a" "f1a395bdc0457e70e9e12e8e6d7b25d1bdbf169802d745687dd5bfe07bf9ca37"` Dec 14 19:59:23.407 INFO [stderr] usermod: no changes Dec 14 19:59:23.430 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently Dec 14 19:59:23.430 INFO [stderr] disables Cargo from automatically inferring other test targets. Dec 14 19:59:23.430 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 14 19:59:23.430 INFO [stderr] files will be included as a test target: Dec 14 19:59:23.430 INFO [stderr] Dec 14 19:59:23.430 INFO [stderr] * /source/tests/deploy.rs Dec 14 19:59:23.430 INFO [stderr] * /source/tests/logs.rs Dec 14 19:59:23.430 INFO [stderr] * /source/tests/support.rs Dec 14 19:59:23.430 INFO [stderr] * /source/tests/auth.rs Dec 14 19:59:23.430 INFO [stderr] * /source/tests/repo.rs Dec 14 19:59:23.430 INFO [stderr] Dec 14 19:59:23.430 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 14 19:59:23.430 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself Dec 14 19:59:23.430 INFO [stderr] and disable this warning by adding `autotests = false` to your [package] Dec 14 19:59:23.430 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 14 19:59:23.430 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 14 19:59:23.430 INFO [stderr] Dec 14 19:59:23.430 INFO [stderr] For more information on this warning you can consult Dec 14 19:59:23.430 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 14 19:59:23.831 INFO [stderr] Compiling mockito v0.2.5 Dec 14 19:59:23.831 INFO [stderr] Compiling ws v0.7.9 Dec 14 19:59:27.908 INFO [stderr] Compiling sherpa v0.4.0 (/source) Dec 14 19:59:35.282 INFO [stderr] error: 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 14 19:59:35.282 INFO [stderr] --> src/config.rs:98:21 Dec 14 19:59:35.282 INFO [stderr] | Dec 14 19:59:35.282 INFO [stderr] 98 | let home_path = env::home_dir().unwrap(); Dec 14 19:59:35.282 INFO [stderr] | ^^^^^^^^^^^^^ Dec 14 19:59:35.282 INFO [stderr] | Dec 14 19:59:35.282 INFO [stderr] note: lint level defined here Dec 14 19:59:35.282 INFO [stderr] --> src/lib.rs:1:9 Dec 14 19:59:35.282 INFO [stderr] | Dec 14 19:59:35.282 INFO [stderr] 1 | #![deny(warnings)] Dec 14 19:59:35.282 INFO [stderr] | ^^^^^^^^ Dec 14 19:59:35.282 INFO [stderr] = note: #[deny(deprecated)] implied by #[deny(warnings)] Dec 14 19:59:35.282 INFO [stderr] Dec 14 19:59:35.760 INFO [stderr] error: aborting due to previous error Dec 14 19:59:35.760 INFO [stderr] Dec 14 19:59:35.794 INFO [stderr] error: Could not compile `sherpa`. Dec 14 19:59:35.795 INFO [stderr] Dec 14 19:59:35.795 INFO [stderr] To learn more, run the command again with --verbose. Dec 14 19:59:35.795 INFO [stderr] su: No module specific data is present Dec 14 19:59:36.302 INFO running `"docker" "inspect" "f1a395bdc0457e70e9e12e8e6d7b25d1bdbf169802d745687dd5bfe07bf9ca37"` Dec 14 19:59:36.593 INFO running `"docker" "rm" "-f" "f1a395bdc0457e70e9e12e8e6d7b25d1bdbf169802d745687dd5bfe07bf9ca37"` Dec 14 19:59:36.953 INFO [stdout] f1a395bdc0457e70e9e12e8e6d7b25d1bdbf169802d745687dd5bfe07bf9ca37