Nov 28 02:30:30.538 INFO checking kevlarr/rusty-calc against master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5 for pr-56074
Nov 28 02:30:30.538 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-2/master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-56074/master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5:/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 +0b9f19dff1347e29bf4362ab5a8fab84b43023b5-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 02:30:30.804 INFO [stdout] 7030a4da5158007d482ff84464f8804e229bb59ca65c9c8168bccb3482499480
Nov 28 02:30:30.810 INFO running `"docker" "start" "-a" "7030a4da5158007d482ff84464f8804e229bb59ca65c9c8168bccb3482499480"`
Nov 28 02:30:31.708 INFO [stderr] usermod: no changes
Nov 28 02:30:31.778 INFO [stderr]     Checking rustycalc v0.1.0 (/source)
Nov 28 02:30:32.309 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 02:30:32.309 INFO [stderr]    --> src/types/binary.rs:111:9
Nov 28 02:30:32.309 INFO [stderr]     |
Nov 28 02:30:32.309 INFO [stderr] 111 |         write!(f, "0b");
Nov 28 02:30:32.309 INFO [stderr]     |         ^^^^^^^^^^^^^^^^
Nov 28 02:30:32.309 INFO [stderr]     |
Nov 28 02:30:32.309 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 28 02:30:32.309 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 02:30:32.309 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 02:30:32.309 INFO [stderr] 
Nov 28 02:30:32.316 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 02:30:32.316 INFO [stderr]    --> src/types/binary.rs:115:17
Nov 28 02:30:32.316 INFO [stderr]     |
Nov 28 02:30:32.316 INFO [stderr] 115 |                 write!(f, "_");
Nov 28 02:30:32.316 INFO [stderr]     |                 ^^^^^^^^^^^^^^^
Nov 28 02:30:32.316 INFO [stderr]     |
Nov 28 02:30:32.316 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 02:30:32.316 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 02:30:32.316 INFO [stderr] 
Nov 28 02:30:32.768 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 02:30:32.768 INFO [stderr]    --> src/types/binary.rs:111:9
Nov 28 02:30:32.768 INFO [stderr]     |
Nov 28 02:30:32.768 INFO [stderr] 111 |         write!(f, "0b");
Nov 28 02:30:32.768 INFO [stderr]     |         ^^^^^^^^^^^^^^^^
Nov 28 02:30:32.768 INFO [stderr]     |
Nov 28 02:30:32.768 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 28 02:30:32.768 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 02:30:32.768 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 02:30:32.768 INFO [stderr] 
Nov 28 02:30:32.778 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 02:30:32.778 INFO [stderr]    --> src/types/binary.rs:115:17
Nov 28 02:30:32.779 INFO [stderr]     |
Nov 28 02:30:32.779 INFO [stderr] 115 |                 write!(f, "_");
Nov 28 02:30:32.779 INFO [stderr]     |                 ^^^^^^^^^^^^^^^
Nov 28 02:30:32.779 INFO [stderr]     |
Nov 28 02:30:32.779 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 02:30:32.779 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 02:30:32.779 INFO [stderr] 
Nov 28 02:30:33.212 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.47s
Nov 28 02:30:33.212 INFO [stderr] su: No module specific data is present
Nov 28 02:30:33.722 INFO running `"docker" "inspect" "7030a4da5158007d482ff84464f8804e229bb59ca65c9c8168bccb3482499480"`
Nov 28 02:30:34.034 INFO running `"docker" "rm" "-f" "7030a4da5158007d482ff84464f8804e229bb59ca65c9c8168bccb3482499480"`
Nov 28 02:30:34.268 INFO [stdout] 7030a4da5158007d482ff84464f8804e229bb59ca65c9c8168bccb3482499480