Nov 30 21:15:07.943 INFO checking hexyl-0.2.0 against try#32252761328f59ccfadb1bafb8148c685bc830b3 for pr-56323
Nov 30 21:15:07.943 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56323/worker-4/try#32252761328f59ccfadb1bafb8148c685bc830b3:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56323/try#32252761328f59ccfadb1bafb8148c685bc830b3:/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 +32252761328f59ccfadb1bafb8148c685bc830b3-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 21:15:08.120 INFO [stdout] d92c39e52979b6a4a167c758d8a22b3730eae5bba501b1f29d24226d77cd5db7
Nov 30 21:15:08.122 INFO running `"docker" "start" "-a" "d92c39e52979b6a4a167c758d8a22b3730eae5bba501b1f29d24226d77cd5db7"`
Nov 30 21:15:08.628 INFO [stderr] usermod: no changes
Nov 30 21:15:08.688 INFO [stderr]     Checking hexyl v0.2.0 (/source)
Nov 30 21:15:10.219 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 21:15:10.219 INFO [stderr]   --> src/main.rs:92:9
Nov 30 21:15:10.219 INFO [stderr]    |
Nov 30 21:15:10.219 INFO [stderr] 92 | /         writeln!(
Nov 30 21:15:10.219 INFO [stderr] 93 | |             self.stdout,
Nov 30 21:15:10.219 INFO [stderr] 94 | |             "┌{}┬{}┬{}┬{}┐",
Nov 30 21:15:10.219 INFO [stderr] 95 | |             "─".repeat(3 * 8 + 1),
Nov 30 21:15:10.220 INFO [stderr] ...  |
Nov 30 21:15:10.220 INFO [stderr] 98 | |             "─".repeat(8)
Nov 30 21:15:10.220 INFO [stderr] 99 | |         );
Nov 30 21:15:10.220 INFO [stderr]    | |__________^
Nov 30 21:15:10.220 INFO [stderr]    |
Nov 30 21:15:10.220 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Nov 30 21:15:10.220 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 21:15:10.220 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 21:15:10.221 INFO [stderr] 
Nov 30 21:15:10.221 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 21:15:10.221 INFO [stderr]    --> src/main.rs:103:9
Nov 30 21:15:10.221 INFO [stderr]     |
Nov 30 21:15:10.221 INFO [stderr] 103 | /         writeln!(
Nov 30 21:15:10.221 INFO [stderr] 104 | |             self.stdout,
Nov 30 21:15:10.221 INFO [stderr] 105 | |             "└{}┴{}┴{}┴{}┘",
Nov 30 21:15:10.221 INFO [stderr] 106 | |             "─".repeat(3 * 8 + 1),
Nov 30 21:15:10.221 INFO [stderr] ...   |
Nov 30 21:15:10.222 INFO [stderr] 109 | |             "─".repeat(8)
Nov 30 21:15:10.222 INFO [stderr] 110 | |         );
Nov 30 21:15:10.222 INFO [stderr]     | |__________^
Nov 30 21:15:10.222 INFO [stderr]     |
Nov 30 21:15:10.222 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 21:15:10.222 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 21:15:10.222 INFO [stderr] 
Nov 30 21:15:10.222 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 21:15:10.222 INFO [stderr]    --> src/main.rs:115:13
Nov 30 21:15:10.222 INFO [stderr]     |
Nov 30 21:15:10.222 INFO [stderr] 115 |             write!(self.stdout, "│ ");
Nov 30 21:15:10.222 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 30 21:15:10.222 INFO [stderr]     |
Nov 30 21:15:10.222 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 21:15:10.222 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 21:15:10.222 INFO [stderr] 
Nov 30 21:15:10.222 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 21:15:10.222 INFO [stderr]    --> src/main.rs:159:17
Nov 30 21:15:10.222 INFO [stderr]     |
Nov 30 21:15:10.222 INFO [stderr] 159 |                 write!(self.stdout, "┊");
Nov 30 21:15:10.222 INFO [stderr]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 30 21:15:10.222 INFO [stderr]     |
Nov 30 21:15:10.222 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 21:15:10.222 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 21:15:10.222 INFO [stderr] 
Nov 30 21:15:10.287 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 21:15:10.287 INFO [stderr]   --> src/main.rs:92:9
Nov 30 21:15:10.287 INFO [stderr]    |
Nov 30 21:15:10.287 INFO [stderr] 92 | /         writeln!(
Nov 30 21:15:10.287 INFO [stderr] 93 | |             self.stdout,
Nov 30 21:15:10.287 INFO [stderr] 94 | |             "┌{}┬{}┬{}┬{}┐",
Nov 30 21:15:10.287 INFO [stderr] 95 | |             "─".repeat(3 * 8 + 1),
Nov 30 21:15:10.287 INFO [stderr] ...  |
Nov 30 21:15:10.287 INFO [stderr] 98 | |             "─".repeat(8)
Nov 30 21:15:10.287 INFO [stderr] 99 | |         );
Nov 30 21:15:10.287 INFO [stderr]    | |__________^
Nov 30 21:15:10.287 INFO [stderr]    |
Nov 30 21:15:10.288 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Nov 30 21:15:10.288 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 21:15:10.288 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 21:15:10.288 INFO [stderr] 
Nov 30 21:15:10.288 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 21:15:10.288 INFO [stderr]    --> src/main.rs:103:9
Nov 30 21:15:10.289 INFO [stderr]     |
Nov 30 21:15:10.289 INFO [stderr] 103 | /         writeln!(
Nov 30 21:15:10.289 INFO [stderr] 104 | |             self.stdout,
Nov 30 21:15:10.289 INFO [stderr] 105 | |             "└{}┴{}┴{}┴{}┘",
Nov 30 21:15:10.289 INFO [stderr] 106 | |             "─".repeat(3 * 8 + 1),
Nov 30 21:15:10.289 INFO [stderr] ...   |
Nov 30 21:15:10.289 INFO [stderr] 109 | |             "─".repeat(8)
Nov 30 21:15:10.289 INFO [stderr] 110 | |         );
Nov 30 21:15:10.289 INFO [stderr]     | |__________^
Nov 30 21:15:10.289 INFO [stderr]     |
Nov 30 21:15:10.289 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 21:15:10.289 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 21:15:10.290 INFO [stderr] 
Nov 30 21:15:10.290 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 21:15:10.290 INFO [stderr]    --> src/main.rs:115:13
Nov 30 21:15:10.290 INFO [stderr]     |
Nov 30 21:15:10.290 INFO [stderr] 115 |             write!(self.stdout, "│ ");
Nov 30 21:15:10.290 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 30 21:15:10.290 INFO [stderr]     |
Nov 30 21:15:10.290 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 21:15:10.290 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 21:15:10.290 INFO [stderr] 
Nov 30 21:15:10.291 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 21:15:10.291 INFO [stderr]    --> src/main.rs:159:17
Nov 30 21:15:10.291 INFO [stderr]     |
Nov 30 21:15:10.291 INFO [stderr] 159 |                 write!(self.stdout, "┊");
Nov 30 21:15:10.291 INFO [stderr]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 30 21:15:10.291 INFO [stderr]     |
Nov 30 21:15:10.291 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 21:15:10.292 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 21:15:10.292 INFO [stderr] 
Nov 30 21:15:10.344 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.69s
Nov 30 21:15:10.344 INFO [stderr] su: No module specific data is present
Nov 30 21:15:11.040 INFO running `"docker" "inspect" "d92c39e52979b6a4a167c758d8a22b3730eae5bba501b1f29d24226d77cd5db7"`
Nov 30 21:15:11.135 INFO running `"docker" "rm" "-f" "d92c39e52979b6a4a167c758d8a22b3730eae5bba501b1f29d24226d77cd5db7"`
Nov 30 21:15:11.227 INFO [stdout] d92c39e52979b6a4a167c758d8a22b3730eae5bba501b1f29d24226d77cd5db7