Dec 04 21:45:20.224 INFO checking blinry/habitctl against try#1df97983eb2057dc6a8f7eb364e263b51ae23230 for pr-56481
Dec 04 21:45:20.224 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56481/worker-6/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56481/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/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 +1df97983eb2057dc6a8f7eb364e263b51ae23230-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"`
Dec 04 21:45:20.724 INFO [stdout] c3fc3c5ca474d679cbe16711b96bca293a81276f410602e1ee10bc883e54a607
Dec 04 21:45:20.726 INFO running `"docker" "start" "-a" "c3fc3c5ca474d679cbe16711b96bca293a81276f410602e1ee10bc883e54a607"`
Dec 04 21:45:22.423 INFO [stderr] usermod: no changes
Dec 04 21:45:22.575 INFO [stderr]     Checking habitctl v0.1.0 (/source)
Dec 04 21:45:24.219 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 21:45:24.219 INFO [stderr]    --> src/main.rs:133:13
Dec 04 21:45:24.219 INFO [stderr]     |
Dec 04 21:45:24.219 INFO [stderr] 133 | /             write!(
Dec 04 21:45:24.219 INFO [stderr] 134 | |                 &file,
Dec 04 21:45:24.219 INFO [stderr] 135 | |                 "# The numbers specifies how often you want to do a habit:\n"
Dec 04 21:45:24.219 INFO [stderr] 136 | |             );
Dec 04 21:45:24.219 INFO [stderr]     | |______________^
Dec 04 21:45:24.219 INFO [stderr]     |
Dec 04 21:45:24.219 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Dec 04 21:45:24.219 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 21:45:24.219 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)
Dec 04 21:45:24.219 INFO [stderr] 
Dec 04 21:45:24.219 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 21:45:24.219 INFO [stderr]    --> src/main.rs:137:13
Dec 04 21:45:24.219 INFO [stderr]     |
Dec 04 21:45:24.219 INFO [stderr] 137 | /             write!(
Dec 04 21:45:24.219 INFO [stderr] 138 | |                 &file,
Dec 04 21:45:24.219 INFO [stderr] 139 | |                 "# 1 means daily, 7 means weekly, 0 means you're just tracking the habit. Some examples:\n"
Dec 04 21:45:24.219 INFO [stderr] 140 | |             );
Dec 04 21:45:24.219 INFO [stderr]     | |______________^
Dec 04 21:45:24.219 INFO [stderr]     |
Dec 04 21:45:24.219 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 21:45:24.219 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)
Dec 04 21:45:24.219 INFO [stderr] 
Dec 04 21:45:24.219 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 21:45:24.219 INFO [stderr]    --> src/main.rs:141:13
Dec 04 21:45:24.219 INFO [stderr]     |
Dec 04 21:45:24.219 INFO [stderr] 141 | /             write!(
Dec 04 21:45:24.219 INFO [stderr] 142 | |                 &file,
Dec 04 21:45:24.219 INFO [stderr] 143 | |                 "\n# 1 Meditated\n# 7 Cleaned the apartment\n# 0 Had a headache\n# 1 Used habitctl\n"
Dec 04 21:45:24.219 INFO [stderr] 144 | |             );
Dec 04 21:45:24.219 INFO [stderr]     | |______________^
Dec 04 21:45:24.219 INFO [stderr]     |
Dec 04 21:45:24.219 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 21:45:24.219 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)
Dec 04 21:45:24.219 INFO [stderr] 
Dec 04 21:45:24.344 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 21:45:24.344 INFO [stderr]    --> src/main.rs:133:13
Dec 04 21:45:24.344 INFO [stderr]     |
Dec 04 21:45:24.344 INFO [stderr] 133 | /             write!(
Dec 04 21:45:24.344 INFO [stderr] 134 | |                 &file,
Dec 04 21:45:24.344 INFO [stderr] 135 | |                 "# The numbers specifies how often you want to do a habit:\n"
Dec 04 21:45:24.344 INFO [stderr] 136 | |             );
Dec 04 21:45:24.344 INFO [stderr]     | |______________^
Dec 04 21:45:24.344 INFO [stderr]     |
Dec 04 21:45:24.344 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Dec 04 21:45:24.344 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 21:45:24.344 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)
Dec 04 21:45:24.344 INFO [stderr] 
Dec 04 21:45:24.344 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 21:45:24.344 INFO [stderr]    --> src/main.rs:137:13
Dec 04 21:45:24.344 INFO [stderr]     |
Dec 04 21:45:24.344 INFO [stderr] 137 | /             write!(
Dec 04 21:45:24.344 INFO [stderr] 138 | |                 &file,
Dec 04 21:45:24.344 INFO [stderr] 139 | |                 "# 1 means daily, 7 means weekly, 0 means you're just tracking the habit. Some examples:\n"
Dec 04 21:45:24.344 INFO [stderr] 140 | |             );
Dec 04 21:45:24.344 INFO [stderr]     | |______________^
Dec 04 21:45:24.344 INFO [stderr]     |
Dec 04 21:45:24.344 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 21:45:24.344 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)
Dec 04 21:45:24.344 INFO [stderr] 
Dec 04 21:45:24.344 INFO [stderr] warning: unused `std::result::Result` that must be used
Dec 04 21:45:24.344 INFO [stderr]    --> src/main.rs:141:13
Dec 04 21:45:24.344 INFO [stderr]     |
Dec 04 21:45:24.344 INFO [stderr] 141 | /             write!(
Dec 04 21:45:24.344 INFO [stderr] 142 | |                 &file,
Dec 04 21:45:24.344 INFO [stderr] 143 | |                 "\n# 1 Meditated\n# 7 Cleaned the apartment\n# 0 Had a headache\n# 1 Used habitctl\n"
Dec 04 21:45:24.344 INFO [stderr] 144 | |             );
Dec 04 21:45:24.344 INFO [stderr]     | |______________^
Dec 04 21:45:24.344 INFO [stderr]     |
Dec 04 21:45:24.344 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Dec 04 21:45:24.344 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)
Dec 04 21:45:24.344 INFO [stderr] 
Dec 04 21:45:24.387 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.93s
Dec 04 21:45:24.387 INFO [stderr] su: No module specific data is present
Dec 04 21:45:24.904 INFO running `"docker" "inspect" "c3fc3c5ca474d679cbe16711b96bca293a81276f410602e1ee10bc883e54a607"`
Dec 04 21:45:25.215 INFO running `"docker" "rm" "-f" "c3fc3c5ca474d679cbe16711b96bca293a81276f410602e1ee10bc883e54a607"`
Dec 04 21:45:25.471 INFO [stdout] c3fc3c5ca474d679cbe16711b96bca293a81276f410602e1ee10bc883e54a607