Nov 28 08:36:22.241 INFO checking blinry/habitctl against try#db42d4dad33013eba11ef37342ad9f614e5652b8 for pr-56074
Nov 28 08:36:22.241 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-2/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 08:36:22.774 INFO [stdout] 441693a6c1809fd433fef55de3ee6b15c16bbcab5503cbd6cad4812d32983ab3
Nov 28 08:36:22.777 INFO running `"docker" "start" "-a" "441693a6c1809fd433fef55de3ee6b15c16bbcab5503cbd6cad4812d32983ab3"`
Nov 28 08:36:24.169 INFO [stderr] usermod: no changes
Nov 28 08:36:24.296 INFO [stderr]     Checking habitctl v0.1.0 (/source)
Nov 28 08:36:25.968 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 08:36:25.968 INFO [stderr]    --> src/main.rs:133:13
Nov 28 08:36:25.968 INFO [stderr]     |
Nov 28 08:36:25.968 INFO [stderr] 133 | /             write!(
Nov 28 08:36:25.968 INFO [stderr] 134 | |                 &file,
Nov 28 08:36:25.968 INFO [stderr] 135 | |                 "# The numbers specifies how often you want to do a habit:\n"
Nov 28 08:36:25.968 INFO [stderr] 136 | |             );
Nov 28 08:36:25.968 INFO [stderr]     | |______________^
Nov 28 08:36:25.968 INFO [stderr]     |
Nov 28 08:36:25.968 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 28 08:36:25.968 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 08:36:25.968 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 28 08:36:25.968 INFO [stderr] 
Nov 28 08:36:25.968 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 08:36:25.969 INFO [stderr]    --> src/main.rs:137:13
Nov 28 08:36:25.969 INFO [stderr]     |
Nov 28 08:36:25.969 INFO [stderr] 137 | /             write!(
Nov 28 08:36:25.969 INFO [stderr] 138 | |                 &file,
Nov 28 08:36:25.969 INFO [stderr] 139 | |                 "# 1 means daily, 7 means weekly, 0 means you're just tracking the habit. Some examples:\n"
Nov 28 08:36:25.969 INFO [stderr] 140 | |             );
Nov 28 08:36:25.969 INFO [stderr]     | |______________^
Nov 28 08:36:25.969 INFO [stderr]     |
Nov 28 08:36:25.969 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 08:36:25.969 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 28 08:36:25.969 INFO [stderr] 
Nov 28 08:36:25.969 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 08:36:25.969 INFO [stderr]    --> src/main.rs:141:13
Nov 28 08:36:25.969 INFO [stderr]     |
Nov 28 08:36:25.969 INFO [stderr] 141 | /             write!(
Nov 28 08:36:25.969 INFO [stderr] 142 | |                 &file,
Nov 28 08:36:25.969 INFO [stderr] 143 | |                 "\n# 1 Meditated\n# 7 Cleaned the apartment\n# 0 Had a headache\n# 1 Used habitctl\n"
Nov 28 08:36:25.969 INFO [stderr] 144 | |             );
Nov 28 08:36:25.969 INFO [stderr]     | |______________^
Nov 28 08:36:25.969 INFO [stderr]     |
Nov 28 08:36:25.969 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 08:36:25.969 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 28 08:36:25.969 INFO [stderr] 
Nov 28 08:36:26.020 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 08:36:26.020 INFO [stderr]    --> src/main.rs:133:13
Nov 28 08:36:26.020 INFO [stderr]     |
Nov 28 08:36:26.020 INFO [stderr] 133 | /             write!(
Nov 28 08:36:26.020 INFO [stderr] 134 | |                 &file,
Nov 28 08:36:26.020 INFO [stderr] 135 | |                 "# The numbers specifies how often you want to do a habit:\n"
Nov 28 08:36:26.020 INFO [stderr] 136 | |             );
Nov 28 08:36:26.020 INFO [stderr]     | |______________^
Nov 28 08:36:26.020 INFO [stderr]     |
Nov 28 08:36:26.020 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 28 08:36:26.020 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 08:36:26.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 28 08:36:26.020 INFO [stderr] 
Nov 28 08:36:26.020 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 08:36:26.020 INFO [stderr]    --> src/main.rs:137:13
Nov 28 08:36:26.021 INFO [stderr]     |
Nov 28 08:36:26.021 INFO [stderr] 137 | /             write!(
Nov 28 08:36:26.021 INFO [stderr] 138 | |                 &file,
Nov 28 08:36:26.021 INFO [stderr] 139 | |                 "# 1 means daily, 7 means weekly, 0 means you're just tracking the habit. Some examples:\n"
Nov 28 08:36:26.021 INFO [stderr] 140 | |             );
Nov 28 08:36:26.021 INFO [stderr]     | |______________^
Nov 28 08:36:26.021 INFO [stderr]     |
Nov 28 08:36:26.021 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 08:36:26.021 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 28 08:36:26.021 INFO [stderr] 
Nov 28 08:36:26.021 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 08:36:26.021 INFO [stderr]    --> src/main.rs:141:13
Nov 28 08:36:26.021 INFO [stderr]     |
Nov 28 08:36:26.021 INFO [stderr] 141 | /             write!(
Nov 28 08:36:26.021 INFO [stderr] 142 | |                 &file,
Nov 28 08:36:26.021 INFO [stderr] 143 | |                 "\n# 1 Meditated\n# 7 Cleaned the apartment\n# 0 Had a headache\n# 1 Used habitctl\n"
Nov 28 08:36:26.021 INFO [stderr] 144 | |             );
Nov 28 08:36:26.021 INFO [stderr]     | |______________^
Nov 28 08:36:26.021 INFO [stderr]     |
Nov 28 08:36:26.021 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 08:36:26.021 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 28 08:36:26.021 INFO [stderr] 
Nov 28 08:36:26.060 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.85s
Nov 28 08:36:26.061 INFO [stderr] su: No module specific data is present
Nov 28 08:36:27.032 INFO running `"docker" "inspect" "441693a6c1809fd433fef55de3ee6b15c16bbcab5503cbd6cad4812d32983ab3"`
Nov 28 08:36:27.306 INFO running `"docker" "rm" "-f" "441693a6c1809fd433fef55de3ee6b15c16bbcab5503cbd6cad4812d32983ab3"`
Nov 28 08:36:27.518 INFO [stdout] 441693a6c1809fd433fef55de3ee6b15c16bbcab5503cbd6cad4812d32983ab3