Nov 30 06:08:57.485 INFO checking blinry/habitctl against try#32252761328f59ccfadb1bafb8148c685bc830b3 for pr-56323
Nov 30 06:08:57.485 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56323/worker-0/try#32252761328f59ccfadb1bafb8148c685bc830b3:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 06:08:57.908 INFO [stdout] 338273a8900818982a90197d91e1b593b3283c52a31d6b143cc3e43a992106db
Nov 30 06:08:57.916 INFO running `"docker" "start" "-a" "338273a8900818982a90197d91e1b593b3283c52a31d6b143cc3e43a992106db"`
Nov 30 06:08:59.916 INFO [stderr] usermod: no changes
Nov 30 06:09:00.012 INFO [stderr]     Checking habitctl v0.1.0 (/source)
Nov 30 06:09:01.945 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 06:09:01.946 INFO [stderr]    --> src/main.rs:133:13
Nov 30 06:09:01.946 INFO [stderr]     |
Nov 30 06:09:01.946 INFO [stderr] 133 | /             write!(
Nov 30 06:09:01.946 INFO [stderr] 134 | |                 &file,
Nov 30 06:09:01.946 INFO [stderr] 135 | |                 "# The numbers specifies how often you want to do a habit:\n"
Nov 30 06:09:01.946 INFO [stderr] 136 | |             );
Nov 30 06:09:01.946 INFO [stderr]     | |______________^
Nov 30 06:09:01.946 INFO [stderr]     |
Nov 30 06:09:01.946 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 30 06:09:01.946 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 06:09:01.946 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 06:09:01.946 INFO [stderr] 
Nov 30 06:09:01.946 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 06:09:01.946 INFO [stderr]    --> src/main.rs:137:13
Nov 30 06:09:01.946 INFO [stderr]     |
Nov 30 06:09:01.946 INFO [stderr] 137 | /             write!(
Nov 30 06:09:01.946 INFO [stderr] 138 | |                 &file,
Nov 30 06:09:01.947 INFO [stderr] 139 | |                 "# 1 means daily, 7 means weekly, 0 means you're just tracking the habit. Some examples:\n"
Nov 30 06:09:01.947 INFO [stderr] 140 | |             );
Nov 30 06:09:01.947 INFO [stderr]     | |______________^
Nov 30 06:09:01.947 INFO [stderr]     |
Nov 30 06:09:01.947 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 06:09:01.947 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 06:09:01.947 INFO [stderr] 
Nov 30 06:09:01.947 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 06:09:01.947 INFO [stderr]    --> src/main.rs:141:13
Nov 30 06:09:01.947 INFO [stderr]     |
Nov 30 06:09:01.947 INFO [stderr] 141 | /             write!(
Nov 30 06:09:01.947 INFO [stderr] 142 | |                 &file,
Nov 30 06:09:01.947 INFO [stderr] 143 | |                 "\n# 1 Meditated\n# 7 Cleaned the apartment\n# 0 Had a headache\n# 1 Used habitctl\n"
Nov 30 06:09:01.947 INFO [stderr] 144 | |             );
Nov 30 06:09:01.947 INFO [stderr]     | |______________^
Nov 30 06:09:01.947 INFO [stderr]     |
Nov 30 06:09:01.947 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 06:09:01.947 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 06:09:01.947 INFO [stderr] 
Nov 30 06:09:02.003 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 06:09:02.003 INFO [stderr]    --> src/main.rs:133:13
Nov 30 06:09:02.003 INFO [stderr]     |
Nov 30 06:09:02.003 INFO [stderr] 133 | /             write!(
Nov 30 06:09:02.003 INFO [stderr] 134 | |                 &file,
Nov 30 06:09:02.003 INFO [stderr] 135 | |                 "# The numbers specifies how often you want to do a habit:\n"
Nov 30 06:09:02.004 INFO [stderr] 136 | |             );
Nov 30 06:09:02.004 INFO [stderr]     | |______________^
Nov 30 06:09:02.004 INFO [stderr]     |
Nov 30 06:09:02.004 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 30 06:09:02.004 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 06:09:02.004 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 06:09:02.004 INFO [stderr] 
Nov 30 06:09:02.004 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 06:09:02.004 INFO [stderr]    --> src/main.rs:137:13
Nov 30 06:09:02.005 INFO [stderr]     |
Nov 30 06:09:02.005 INFO [stderr] 137 | /             write!(
Nov 30 06:09:02.005 INFO [stderr] 138 | |                 &file,
Nov 30 06:09:02.005 INFO [stderr] 139 | |                 "# 1 means daily, 7 means weekly, 0 means you're just tracking the habit. Some examples:\n"
Nov 30 06:09:02.005 INFO [stderr] 140 | |             );
Nov 30 06:09:02.005 INFO [stderr]     | |______________^
Nov 30 06:09:02.005 INFO [stderr]     |
Nov 30 06:09:02.005 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 06:09:02.005 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 06:09:02.005 INFO [stderr] 
Nov 30 06:09:02.006 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 06:09:02.006 INFO [stderr]    --> src/main.rs:141:13
Nov 30 06:09:02.006 INFO [stderr]     |
Nov 30 06:09:02.006 INFO [stderr] 141 | /             write!(
Nov 30 06:09:02.006 INFO [stderr] 142 | |                 &file,
Nov 30 06:09:02.006 INFO [stderr] 143 | |                 "\n# 1 Meditated\n# 7 Cleaned the apartment\n# 0 Had a headache\n# 1 Used habitctl\n"
Nov 30 06:09:02.006 INFO [stderr] 144 | |             );
Nov 30 06:09:02.006 INFO [stderr]     | |______________^
Nov 30 06:09:02.006 INFO [stderr]     |
Nov 30 06:09:02.007 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 06:09:02.007 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 06:09:02.007 INFO [stderr] 
Nov 30 06:09:02.035 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.09s
Nov 30 06:09:02.039 INFO [stderr] su: No module specific data is present
Nov 30 06:09:02.843 INFO running `"docker" "inspect" "338273a8900818982a90197d91e1b593b3283c52a31d6b143cc3e43a992106db"`
Nov 30 06:09:03.158 INFO running `"docker" "rm" "-f" "338273a8900818982a90197d91e1b593b3283c52a31d6b143cc3e43a992106db"`
Nov 30 06:09:03.452 INFO [stdout] 338273a8900818982a90197d91e1b593b3283c52a31d6b143cc3e43a992106db