Nov 30 13:16:49.796 INFO checking vtkio-0.1.6 against master#a49316ddc99d9d595193557fc899f6c52e4d9af9 for pr-56323 Nov 30 13:16:49.796 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56323/worker-3/master#a49316ddc99d9d595193557fc899f6c52e4d9af9:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56323/master#a49316ddc99d9d595193557fc899f6c52e4d9af9:/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 +a49316ddc99d9d595193557fc899f6c52e4d9af9-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 30 13:16:50.264 INFO [stdout] bfb696b69a321fe70ee400d5ae728fdc8ed9ad59a6e2a6dcc00dd2e9b53355f3 Nov 30 13:16:50.270 INFO running `"docker" "start" "-a" "bfb696b69a321fe70ee400d5ae728fdc8ed9ad59a6e2a6dcc00dd2e9b53355f3"` Nov 30 13:16:51.408 INFO [stderr] usermod: no changes Nov 30 13:16:51.517 INFO [stderr] Checking reinterpret v0.1.2 Nov 30 13:16:52.040 INFO [stderr] Checking data-buffer v0.4.2 Nov 30 13:16:52.948 INFO [stderr] Checking vtkio v0.1.6 (/source) Nov 30 13:17:00.019 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 30 13:17:00.019 INFO [stderr] --> src/writer.rs:40:17 Nov 30 13:17:00.019 INFO [stderr] | Nov 30 13:17:00.019 INFO [stderr] 40 | write!(self, "\n"); Nov 30 13:17:00.019 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ Nov 30 13:17:00.019 INFO [stderr] | Nov 30 13:17:00.019 INFO [stderr] = note: #[warn(unused_must_use)] on by default Nov 30 13:17:00.019 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 30 13:17:00.019 INFO [stderr] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Nov 30 13:17:00.019 INFO [stderr] Nov 30 13:17:00.019 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 30 13:17:00.019 INFO [stderr] --> src/writer.rs:169:21 Nov 30 13:17:00.019 INFO [stderr] | Nov 30 13:17:00.019 INFO [stderr] 169 | write!(self, "\n"); Nov 30 13:17:00.020 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ Nov 30 13:17:00.020 INFO [stderr] | Nov 30 13:17:00.020 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 30 13:17:00.020 INFO [stderr] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Nov 30 13:17:00.020 INFO [stderr] Nov 30 13:17:00.024 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 30 13:17:00.024 INFO [stderr] --> src/writer.rs:331:13 Nov 30 13:17:00.024 INFO [stderr] | Nov 30 13:17:00.024 INFO [stderr] 331 | write!(self, "\n"); Nov 30 13:17:00.024 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ Nov 30 13:17:00.024 INFO [stderr] | Nov 30 13:17:00.024 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 30 13:17:00.024 INFO [stderr] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Nov 30 13:17:00.024 INFO [stderr] Nov 30 13:17:00.784 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 30 13:17:00.784 INFO [stderr] --> src/writer.rs:40:17 Nov 30 13:17:00.784 INFO [stderr] | Nov 30 13:17:00.784 INFO [stderr] 40 | write!(self, "\n"); Nov 30 13:17:00.784 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ Nov 30 13:17:00.784 INFO [stderr] | Nov 30 13:17:00.784 INFO [stderr] = note: #[warn(unused_must_use)] on by default Nov 30 13:17:00.784 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 30 13:17:00.784 INFO [stderr] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Nov 30 13:17:00.784 INFO [stderr] Nov 30 13:17:00.784 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 30 13:17:00.784 INFO [stderr] --> src/writer.rs:169:21 Nov 30 13:17:00.784 INFO [stderr] | Nov 30 13:17:00.784 INFO [stderr] 169 | write!(self, "\n"); Nov 30 13:17:00.784 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ Nov 30 13:17:00.784 INFO [stderr] | Nov 30 13:17:00.784 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 30 13:17:00.784 INFO [stderr] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Nov 30 13:17:00.784 INFO [stderr] Nov 30 13:17:00.785 INFO [stderr] warning: unused `std::result::Result` that must be used Nov 30 13:17:00.785 INFO [stderr] --> src/writer.rs:331:13 Nov 30 13:17:00.785 INFO [stderr] | Nov 30 13:17:00.785 INFO [stderr] 331 | write!(self, "\n"); Nov 30 13:17:00.785 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ Nov 30 13:17:00.785 INFO [stderr] | Nov 30 13:17:00.785 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Nov 30 13:17:00.785 INFO [stderr] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Nov 30 13:17:00.785 INFO [stderr] Nov 30 13:17:02.380 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 10.95s Nov 30 13:17:02.393 INFO [stderr] su: No module specific data is present Nov 30 13:17:03.588 INFO running `"docker" "inspect" "bfb696b69a321fe70ee400d5ae728fdc8ed9ad59a6e2a6dcc00dd2e9b53355f3"` Nov 30 13:17:03.942 INFO running `"docker" "rm" "-f" "bfb696b69a321fe70ee400d5ae728fdc8ed9ad59a6e2a6dcc00dd2e9b53355f3"` Nov 30 13:17:04.204 INFO [stdout] bfb696b69a321fe70ee400d5ae728fdc8ed9ad59a6e2a6dcc00dd2e9b53355f3