Dec 15 09:01:54.611 INFO testing hdf5-0.4.1 against try#aa49d8ef14939ddec0e34b346b60174a5673d48f for pr-56550 Dec 15 09:01:54.611 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-4/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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 15 09:01:54.987 INFO [stdout] fa10346a69664cb32c10289898c0394650aa62af76c25fb82e950856dcdc765d Dec 15 09:01:54.995 INFO running `"docker" "start" "-a" "fa10346a69664cb32c10289898c0394650aa62af76c25fb82e950856dcdc765d"` Dec 15 09:01:56.038 INFO [stderr] usermod: no changes Dec 15 09:01:56.086 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently Dec 15 09:01:56.086 INFO [stderr] disables Cargo from automatically inferring other test targets. Dec 15 09:01:56.086 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 15 09:01:56.086 INFO [stderr] files will be included as a test target: Dec 15 09:01:56.086 INFO [stderr] Dec 15 09:01:56.086 INFO [stderr] * /source/tests/write.rs Dec 15 09:01:56.086 INFO [stderr] * /source/tests/encode.rs Dec 15 09:01:56.086 INFO [stderr] Dec 15 09:01:56.086 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 15 09:01:56.086 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself Dec 15 09:01:56.086 INFO [stderr] and disable this warning by adding `autotests = false` to your [package] Dec 15 09:01:56.086 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 15 09:01:56.086 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 15 09:01:56.087 INFO [stderr] Dec 15 09:01:56.087 INFO [stderr] For more information on this warning you can consult Dec 15 09:01:56.087 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 15 09:01:56.132 INFO [stderr] Compiling hdf5-sys v0.4.1 Dec 15 09:01:58.719 INFO [stderr] Compiling hdf5 v0.4.1 (/source) Dec 15 09:02:00.191 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.12s Dec 15 09:02:00.200 INFO [stderr] su: No module specific data is present Dec 15 09:02:00.667 INFO running `"docker" "inspect" "fa10346a69664cb32c10289898c0394650aa62af76c25fb82e950856dcdc765d"` Dec 15 09:02:00.956 INFO running `"docker" "rm" "-f" "fa10346a69664cb32c10289898c0394650aa62af76c25fb82e950856dcdc765d"` Dec 15 09:02:01.184 INFO [stdout] fa10346a69664cb32c10289898c0394650aa62af76c25fb82e950856dcdc765d Dec 15 09:02:01.195 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-4/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-alt test --frozen --no-run" "-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 15 09:02:01.602 INFO [stdout] d865121c0fc056e6e45182eb85efdf8966d5622316733274f99f6559eab3b268 Dec 15 09:02:01.604 INFO running `"docker" "start" "-a" "d865121c0fc056e6e45182eb85efdf8966d5622316733274f99f6559eab3b268"` Dec 15 09:02:02.805 INFO [stderr] usermod: no changes Dec 15 09:02:02.859 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently Dec 15 09:02:02.859 INFO [stderr] disables Cargo from automatically inferring other test targets. Dec 15 09:02:02.859 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 15 09:02:02.859 INFO [stderr] files will be included as a test target: Dec 15 09:02:02.859 INFO [stderr] Dec 15 09:02:02.859 INFO [stderr] * /source/tests/write.rs Dec 15 09:02:02.859 INFO [stderr] * /source/tests/encode.rs Dec 15 09:02:02.859 INFO [stderr] Dec 15 09:02:02.859 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 15 09:02:02.859 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself Dec 15 09:02:02.859 INFO [stderr] and disable this warning by adding `autotests = false` to your [package] Dec 15 09:02:02.859 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 15 09:02:02.859 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 15 09:02:02.859 INFO [stderr] Dec 15 09:02:02.859 INFO [stderr] For more information on this warning you can consult Dec 15 09:02:02.859 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 15 09:02:02.907 INFO [stderr] Compiling hdf5 v0.4.1 (/source) Dec 15 09:02:07.195 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.36s Dec 15 09:02:07.201 INFO [stderr] su: No module specific data is present Dec 15 09:02:07.711 INFO running `"docker" "inspect" "d865121c0fc056e6e45182eb85efdf8966d5622316733274f99f6559eab3b268"` Dec 15 09:02:07.903 INFO running `"docker" "rm" "-f" "d865121c0fc056e6e45182eb85efdf8966d5622316733274f99f6559eab3b268"` Dec 15 09:02:08.122 INFO [stdout] d865121c0fc056e6e45182eb85efdf8966d5622316733274f99f6559eab3b268