Nov 29 18:21:43.635 INFO checking sharkdp/hexyl against master#a49316ddc99d9d595193557fc899f6c52e4d9af9 for pr-56323
Nov 29 18:21:43.636 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56323/worker-7/master#a49316ddc99d9d595193557fc899f6c52e4d9af9:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 29 18:21:44.298 INFO [stdout] eb0e7ffd9441e787c0ec25dc4757bb74f442206e249f63e41600fd0ae6a20525
Nov 29 18:21:44.300 INFO running `"docker" "start" "-a" "eb0e7ffd9441e787c0ec25dc4757bb74f442206e249f63e41600fd0ae6a20525"`
Nov 29 18:21:45.828 INFO [stderr] usermod: no changes
Nov 29 18:21:45.948 INFO [stderr]     Checking hexyl v0.2.0 (/source)
Nov 29 18:21:46.684 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 18:21:46.684 INFO [stderr]   --> src/main.rs:92:9
Nov 29 18:21:46.684 INFO [stderr]    |
Nov 29 18:21:46.684 INFO [stderr] 92 | /         writeln!(
Nov 29 18:21:46.684 INFO [stderr] 93 | |             self.stdout,
Nov 29 18:21:46.684 INFO [stderr] 94 | |             "┌{}┬{}┬{}┬{}┐",
Nov 29 18:21:46.684 INFO [stderr] 95 | |             "─".repeat(3 * 8 + 1),
Nov 29 18:21:46.684 INFO [stderr] ...  |
Nov 29 18:21:46.684 INFO [stderr] 98 | |             "─".repeat(8)
Nov 29 18:21:46.685 INFO [stderr] 99 | |         );
Nov 29 18:21:46.685 INFO [stderr]    | |__________^
Nov 29 18:21:46.685 INFO [stderr]    |
Nov 29 18:21:46.685 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Nov 29 18:21:46.685 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 18:21:46.685 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 29 18:21:46.685 INFO [stderr] 
Nov 29 18:21:46.685 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 18:21:46.685 INFO [stderr]    --> src/main.rs:103:9
Nov 29 18:21:46.685 INFO [stderr]     |
Nov 29 18:21:46.685 INFO [stderr] 103 | /         writeln!(
Nov 29 18:21:46.685 INFO [stderr] 104 | |             self.stdout,
Nov 29 18:21:46.685 INFO [stderr] 105 | |             "└{}┴{}┴{}┴{}┘",
Nov 29 18:21:46.685 INFO [stderr] 106 | |             "─".repeat(3 * 8 + 1),
Nov 29 18:21:46.685 INFO [stderr] ...   |
Nov 29 18:21:46.685 INFO [stderr] 109 | |             "─".repeat(8)
Nov 29 18:21:46.685 INFO [stderr] 110 | |         );
Nov 29 18:21:46.685 INFO [stderr]     | |__________^
Nov 29 18:21:46.685 INFO [stderr]     |
Nov 29 18:21:46.685 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 18:21:46.685 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 29 18:21:46.685 INFO [stderr] 
Nov 29 18:21:46.685 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 18:21:46.685 INFO [stderr]    --> src/main.rs:115:13
Nov 29 18:21:46.685 INFO [stderr]     |
Nov 29 18:21:46.685 INFO [stderr] 115 |             write!(self.stdout, "│ ");
Nov 29 18:21:46.685 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 18:21:46.685 INFO [stderr]     |
Nov 29 18:21:46.685 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 18:21:46.685 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 29 18:21:46.685 INFO [stderr] 
Nov 29 18:21:46.685 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 18:21:46.685 INFO [stderr]    --> src/main.rs:159:17
Nov 29 18:21:46.685 INFO [stderr]     |
Nov 29 18:21:46.685 INFO [stderr] 159 |                 write!(self.stdout, "┊");
Nov 29 18:21:46.685 INFO [stderr]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 18:21:46.685 INFO [stderr]     |
Nov 29 18:21:46.685 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 18:21:46.685 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 29 18:21:46.685 INFO [stderr] 
Nov 29 18:21:46.952 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 18:21:46.952 INFO [stderr]   --> src/main.rs:92:9
Nov 29 18:21:46.952 INFO [stderr]    |
Nov 29 18:21:46.952 INFO [stderr] 92 | /         writeln!(
Nov 29 18:21:46.952 INFO [stderr] 93 | |             self.stdout,
Nov 29 18:21:46.952 INFO [stderr] 94 | |             "┌{}┬{}┬{}┬{}┐",
Nov 29 18:21:46.953 INFO [stderr] 95 | |             "─".repeat(3 * 8 + 1),
Nov 29 18:21:46.953 INFO [stderr] ...  |
Nov 29 18:21:46.953 INFO [stderr] 98 | |             "─".repeat(8)
Nov 29 18:21:46.953 INFO [stderr] 99 | |         );
Nov 29 18:21:46.953 INFO [stderr]    | |__________^
Nov 29 18:21:46.953 INFO [stderr]    |
Nov 29 18:21:46.953 INFO [stderr]    = note: #[warn(unused_must_use)] on by default
Nov 29 18:21:46.953 INFO [stderr]    = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 18:21:46.953 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 29 18:21:46.953 INFO [stderr] 
Nov 29 18:21:46.953 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 18:21:46.953 INFO [stderr]    --> src/main.rs:103:9
Nov 29 18:21:46.953 INFO [stderr]     |
Nov 29 18:21:46.953 INFO [stderr] 103 | /         writeln!(
Nov 29 18:21:46.953 INFO [stderr] 104 | |             self.stdout,
Nov 29 18:21:46.953 INFO [stderr] 105 | |             "└{}┴{}┴{}┴{}┘",
Nov 29 18:21:46.953 INFO [stderr] 106 | |             "─".repeat(3 * 8 + 1),
Nov 29 18:21:46.953 INFO [stderr] ...   |
Nov 29 18:21:46.953 INFO [stderr] 109 | |             "─".repeat(8)
Nov 29 18:21:46.953 INFO [stderr] 110 | |         );
Nov 29 18:21:46.953 INFO [stderr]     | |__________^
Nov 29 18:21:46.953 INFO [stderr]     |
Nov 29 18:21:46.953 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 18:21:46.953 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 29 18:21:46.953 INFO [stderr] 
Nov 29 18:21:46.953 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 18:21:46.953 INFO [stderr]    --> src/main.rs:115:13
Nov 29 18:21:46.953 INFO [stderr]     |
Nov 29 18:21:46.953 INFO [stderr] 115 |             write!(self.stdout, "│ ");
Nov 29 18:21:46.953 INFO [stderr]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 18:21:46.953 INFO [stderr]     |
Nov 29 18:21:46.953 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 18:21:46.953 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 29 18:21:46.953 INFO [stderr] 
Nov 29 18:21:46.953 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 29 18:21:46.953 INFO [stderr]    --> src/main.rs:159:17
Nov 29 18:21:46.953 INFO [stderr]     |
Nov 29 18:21:46.953 INFO [stderr] 159 |                 write!(self.stdout, "┊");
Nov 29 18:21:46.953 INFO [stderr]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 29 18:21:46.953 INFO [stderr]     |
Nov 29 18:21:46.953 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 29 18:21:46.953 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 29 18:21:46.953 INFO [stderr] 
Nov 29 18:21:46.976 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.12s
Nov 29 18:21:46.996 INFO [stderr] su: No module specific data is present
Nov 29 18:21:47.598 INFO running `"docker" "inspect" "eb0e7ffd9441e787c0ec25dc4757bb74f442206e249f63e41600fd0ae6a20525"`
Nov 29 18:21:47.846 INFO running `"docker" "rm" "-f" "eb0e7ffd9441e787c0ec25dc4757bb74f442206e249f63e41600fd0ae6a20525"`
Nov 29 18:21:48.148 INFO [stdout] eb0e7ffd9441e787c0ec25dc4757bb74f442206e249f63e41600fd0ae6a20525