Dec 04 23:59:09.588 INFO checking Sustrak/SISAHex against master#c8ae2de8363be088604ffa2ccba84ff7ad7250bc for pr-56481 Dec 04 23:59:09.588 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56481/worker-6/master#c8ae2de8363be088604ffa2ccba84ff7ad7250bc:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/pr-56481/master#c8ae2de8363be088604ffa2ccba84ff7ad7250bc:/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 +c8ae2de8363be088604ffa2ccba84ff7ad7250bc-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 23:59:10.007 INFO [stdout] b7b4c0008d9f33c51607d8cb1264f7e06b2bd9129f27889ef908cfb0b22e014e Dec 04 23:59:10.009 INFO running `"docker" "start" "-a" "b7b4c0008d9f33c51607d8cb1264f7e06b2bd9129f27889ef908cfb0b22e014e"` Dec 04 23:59:11.287 INFO [stderr] usermod: no changes Dec 04 23:59:11.412 INFO [stderr] Checking compiler v0.1.0 (/source) Dec 04 23:59:13.041 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 23:59:13.041 INFO [stderr] --> src/main.rs:105:9 Dec 04 23:59:13.041 INFO [stderr] | Dec 04 23:59:13.041 INFO [stderr] 105 | writeln!(out_f, "{:01$x}", i32::from_str_radix(&out_s, 2).unwrap(), 4); Dec 04 23:59:13.041 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 04 23:59:13.041 INFO [stderr] | Dec 04 23:59:13.041 INFO [stderr] = note: #[warn(unused_must_use)] on by default Dec 04 23:59:13.041 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 23:59:13.042 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 23:59:13.042 INFO [stderr] Dec 04 23:59:13.042 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 23:59:13.042 INFO [stderr] --> src/main.rs:107:5 Dec 04 23:59:13.042 INFO [stderr] | Dec 04 23:59:13.043 INFO [stderr] 107 | write!(out_f, "FFFF"); Dec 04 23:59:13.043 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ Dec 04 23:59:13.043 INFO [stderr] | Dec 04 23:59:13.044 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 23:59:13.044 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 23:59:13.044 INFO [stderr] Dec 04 23:59:13.054 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 23:59:13.054 INFO [stderr] --> src/main.rs:105:9 Dec 04 23:59:13.059 INFO [stderr] | Dec 04 23:59:13.059 INFO [stderr] 105 | writeln!(out_f, "{:01$x}", i32::from_str_radix(&out_s, 2).unwrap(), 4); Dec 04 23:59:13.059 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 04 23:59:13.062 INFO [stderr] | Dec 04 23:59:13.063 INFO [stderr] = note: #[warn(unused_must_use)] on by default Dec 04 23:59:13.063 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 23:59:13.063 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 23:59:13.063 INFO [stderr] Dec 04 23:59:13.063 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 04 23:59:13.063 INFO [stderr] --> src/main.rs:107:5 Dec 04 23:59:13.063 INFO [stderr] | Dec 04 23:59:13.063 INFO [stderr] 107 | write!(out_f, "FFFF"); Dec 04 23:59:13.063 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ Dec 04 23:59:13.063 INFO [stderr] | Dec 04 23:59:13.063 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 04 23:59:13.063 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 23:59:13.063 INFO [stderr] Dec 04 23:59:13.083 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.74s Dec 04 23:59:13.083 INFO [stderr] su: No module specific data is present Dec 04 23:59:13.417 INFO running `"docker" "inspect" "b7b4c0008d9f33c51607d8cb1264f7e06b2bd9129f27889ef908cfb0b22e014e"` Dec 04 23:59:13.559 INFO running `"docker" "rm" "-f" "b7b4c0008d9f33c51607d8cb1264f7e06b2bd9129f27889ef908cfb0b22e014e"` Dec 04 23:59:13.833 INFO [stdout] b7b4c0008d9f33c51607d8cb1264f7e06b2bd9129f27889ef908cfb0b22e014e