Nov 30 00:06:59.982 INFO checking kevlarr/rusty-calc against try#32252761328f59ccfadb1bafb8148c685bc830b3 for pr-56323
Nov 30 00:06:59.983 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56323/worker-7/try#32252761328f59ccfadb1bafb8148c685bc830b3:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 00:07:00.472 INFO [stdout] 513387bbbf3988d71b0a8511fc83d6766e3a2e3cd9361d516447605a59d4196a
Nov 30 00:07:00.478 INFO running `"docker" "start" "-a" "513387bbbf3988d71b0a8511fc83d6766e3a2e3cd9361d516447605a59d4196a"`
Nov 30 00:07:01.552 INFO [stderr] usermod: no changes
Nov 30 00:07:01.592 INFO [stderr]     Checking rustycalc v0.1.0 (/source)
Nov 30 00:07:02.076 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 00:07:02.076 INFO [stderr]    --> src/types/binary.rs:111:9
Nov 30 00:07:02.076 INFO [stderr]     |
Nov 30 00:07:02.076 INFO [stderr] 111 |         write!(f, "0b");
Nov 30 00:07:02.076 INFO [stderr]     |         ^^^^^^^^^^^^^^^^
Nov 30 00:07:02.076 INFO [stderr]     |
Nov 30 00:07:02.076 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 30 00:07:02.076 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 00:07:02.076 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 00:07:02.076 INFO [stderr] 
Nov 30 00:07:02.076 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 00:07:02.076 INFO [stderr]    --> src/types/binary.rs:115:17
Nov 30 00:07:02.076 INFO [stderr]     |
Nov 30 00:07:02.076 INFO [stderr] 115 |                 write!(f, "_");
Nov 30 00:07:02.076 INFO [stderr]     |                 ^^^^^^^^^^^^^^^
Nov 30 00:07:02.076 INFO [stderr]     |
Nov 30 00:07:02.077 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 00:07:02.077 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 00:07:02.077 INFO [stderr] 
Nov 30 00:07:02.844 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 00:07:02.844 INFO [stderr]    --> src/types/binary.rs:111:9
Nov 30 00:07:02.845 INFO [stderr]     |
Nov 30 00:07:02.845 INFO [stderr] 111 |         write!(f, "0b");
Nov 30 00:07:02.845 INFO [stderr]     |         ^^^^^^^^^^^^^^^^
Nov 30 00:07:02.846 INFO [stderr]     |
Nov 30 00:07:02.846 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 30 00:07:02.846 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 00:07:02.846 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 00:07:02.847 INFO [stderr] 
Nov 30 00:07:02.847 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 30 00:07:02.847 INFO [stderr]    --> src/types/binary.rs:115:17
Nov 30 00:07:02.848 INFO [stderr]     |
Nov 30 00:07:02.848 INFO [stderr] 115 |                 write!(f, "_");
Nov 30 00:07:02.848 INFO [stderr]     |                 ^^^^^^^^^^^^^^^
Nov 30 00:07:02.848 INFO [stderr]     |
Nov 30 00:07:02.849 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 30 00:07:02.849 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 00:07:02.849 INFO [stderr] 
Nov 30 00:07:02.892 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.32s
Nov 30 00:07:02.897 INFO [stderr] su: No module specific data is present
Nov 30 00:07:03.693 INFO running `"docker" "inspect" "513387bbbf3988d71b0a8511fc83d6766e3a2e3cd9361d516447605a59d4196a"`
Nov 30 00:07:03.914 INFO running `"docker" "rm" "-f" "513387bbbf3988d71b0a8511fc83d6766e3a2e3cd9361d516447605a59d4196a"`
Nov 30 00:07:04.248 INFO [stdout] 513387bbbf3988d71b0a8511fc83d6766e3a2e3cd9361d516447605a59d4196a