Nov 28 23:55:56.799 INFO checking hdf5-0.4.1 against try#db42d4dad33013eba11ef37342ad9f614e5652b8 for pr-56074 Nov 28 23:55:56.799 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-5/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-56074/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/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 +db42d4dad33013eba11ef37342ad9f614e5652b8-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 28 23:55:57.266 INFO [stdout] 030603c97d8f92e7e9204fd02610174824398d5fd239f0f54cfa0e423c68077c Nov 28 23:55:57.268 INFO running `"docker" "start" "-a" "030603c97d8f92e7e9204fd02610174824398d5fd239f0f54cfa0e423c68077c"` Nov 28 23:55:58.905 INFO [stderr] usermod: no changes Nov 28 23:55:58.969 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently Nov 28 23:55:58.969 INFO [stderr] disables Cargo from automatically inferring other test targets. Nov 28 23:55:58.969 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 28 23:55:58.969 INFO [stderr] files will be included as a test target: Nov 28 23:55:58.970 INFO [stderr] Nov 28 23:55:58.970 INFO [stderr] * /source/tests/write.rs Nov 28 23:55:58.970 INFO [stderr] * /source/tests/encode.rs Nov 28 23:55:58.970 INFO [stderr] Nov 28 23:55:58.971 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 28 23:55:58.971 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself Nov 28 23:55:58.971 INFO [stderr] and disable this warning by adding `autotests = false` to your [package] Nov 28 23:55:58.971 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 28 23:55:58.972 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 28 23:55:58.972 INFO [stderr] Nov 28 23:55:58.972 INFO [stderr] For more information on this warning you can consult Nov 28 23:55:58.973 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 28 23:55:58.985 INFO [stderr] Compiling hdf5-sys v0.4.1 Nov 28 23:55:58.985 INFO [stderr] Checking temporary v0.6.3 Nov 28 23:56:01.660 INFO [stderr] Checking hdf5 v0.4.1 (/source) Nov 28 23:56:04.011 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 5.06s Nov 28 23:56:04.011 INFO [stderr] su: No module specific data is present Nov 28 23:56:04.798 INFO running `"docker" "inspect" "030603c97d8f92e7e9204fd02610174824398d5fd239f0f54cfa0e423c68077c"` Nov 28 23:56:05.083 INFO running `"docker" "rm" "-f" "030603c97d8f92e7e9204fd02610174824398d5fd239f0f54cfa0e423c68077c"` Nov 28 23:56:05.417 INFO [stdout] 030603c97d8f92e7e9204fd02610174824398d5fd239f0f54cfa0e423c68077c