Nov 02 22:59:45.972 INFO checking zookeeper-0.5.4 against try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7 for pr-55517
Nov 02 22:59:45.974 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55517/worker-1/try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55517/try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7:/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 +dc8b02d6f1e93f212fc39844ea688b634b4a03c7-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 02 22:59:46.433 INFO blam! 6ffe8542980e6ffd59c0b71f44959939ee90851e7f85bd288b4f535357cc6f24
Nov 02 22:59:46.438 INFO running `"docker" "start" "-a" "6ffe8542980e6ffd59c0b71f44959939ee90851e7f85bd288b4f535357cc6f24"`
Nov 02 22:59:47.753 INFO kablam! usermod: no changes
Nov 02 22:59:47.848 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 02 22:59:47.848 INFO kablam! disables Cargo from automatically inferring other test targets.
Nov 02 22:59:47.848 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 22:59:47.848 INFO kablam! files will be included as a test target:
Nov 02 22:59:47.848 INFO kablam! 
Nov 02 22:59:47.848 INFO kablam! * /source/tests/test_zk.rs
Nov 02 22:59:47.848 INFO kablam! * /source/tests/test_recursive.rs
Nov 02 22:59:47.848 INFO kablam! * /source/tests/test_cache.rs
Nov 02 22:59:47.848 INFO kablam! 
Nov 02 22:59:47.848 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 22:59:47.848 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Nov 02 22:59:47.848 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Nov 02 22:59:47.848 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 22:59:47.848 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 22:59:47.848 INFO kablam! 
Nov 02 22:59:47.848 INFO kablam! For more information on this warning you can consult
Nov 02 22:59:47.849 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 22:59:48.004 INFO kablam!    Compiling proc-macro2 v0.4.20
Nov 02 22:59:48.004 INFO kablam!     Checking snowflake v1.3.0
Nov 02 22:59:48.012 INFO kablam!     Checking mio-extras v2.0.5
Nov 02 22:59:56.377 INFO kablam!    Compiling quote v0.6.9
Nov 02 23:00:00.180 INFO kablam!    Compiling syn v0.14.9
Nov 02 23:00:12.284 INFO kablam!    Compiling zookeeper_derive v0.4.0
Nov 02 23:00:16.467 INFO kablam!     Checking zookeeper v0.5.4 (/source)
Nov 02 23:00:19.364 INFO kablam! warning: variant is never constructed: `Shutdown`
Nov 02 23:00:19.364 INFO kablam!   --> src/recipes/cache.rs:41:5
Nov 02 23:00:19.364 INFO kablam!    |
Nov 02 23:00:19.364 INFO kablam! 41 |     Shutdown,
Nov 02 23:00:19.364 INFO kablam!    |     ^^^^^^^^
Nov 02 23:00:19.364 INFO kablam!    |
Nov 02 23:00:19.364 INFO kablam!    = note: #[warn(dead_code)] on by default
Nov 02 23:00:19.364 INFO kablam! 
Nov 02 23:00:20.048 INFO kablam! warning: variant is never constructed: `Shutdown`
Nov 02 23:00:20.049 INFO kablam!   --> src/recipes/cache.rs:41:5
Nov 02 23:00:20.049 INFO kablam!    |
Nov 02 23:00:20.049 INFO kablam! 41 |     Shutdown,
Nov 02 23:00:20.050 INFO kablam!    |     ^^^^^^^^
Nov 02 23:00:20.072 INFO kablam!    |
Nov 02 23:00:20.073 INFO kablam!    = note: #[warn(dead_code)] on by default
Nov 02 23:00:20.073 INFO kablam! 
Nov 02 23:00:22.948 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 35.14s
Nov 02 23:00:22.959 INFO kablam! su: No module specific data is present
Nov 02 23:00:23.688 INFO running `"docker" "rm" "-f" "6ffe8542980e6ffd59c0b71f44959939ee90851e7f85bd288b4f535357cc6f24"`
Nov 02 23:00:23.992 INFO blam! 6ffe8542980e6ffd59c0b71f44959939ee90851e7f85bd288b4f535357cc6f24