Nov 28 11:28:21.789 INFO checking Qwertyman95/Hack-Assembler against try#db42d4dad33013eba11ef37342ad9f614e5652b8 for pr-56074
Nov 28 11:28:21.789 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-2/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-56074/try#db42d4dad33013eba11ef37342ad9f614e5652b8:/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 +db42d4dad33013eba11ef37342ad9f614e5652b8-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 11:28:22.309 INFO [stdout] 374fe6a2bc4b660dd76ac992e55105db3ca73c7b38a8844bc9060eb52e26430f
Nov 28 11:28:22.311 INFO running `"docker" "start" "-a" "374fe6a2bc4b660dd76ac992e55105db3ca73c7b38a8844bc9060eb52e26430f"`
Nov 28 11:28:23.847 INFO [stderr] usermod: no changes
Nov 28 11:28:23.984 INFO [stderr]     Checking assembler v0.1.0 (/source)
Nov 28 11:28:25.276 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 11:28:25.276 INFO [stderr]    --> src/main.rs:128:17
Nov 28 11:28:25.276 INFO [stderr]     |
Nov 28 11:28:25.276 INFO [stderr] 128 |                 writeln!(output_file, "0{:0>15b}", value);
Nov 28 11:28:25.276 INFO [stderr]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 28 11:28:25.277 INFO [stderr]     |
Nov 28 11:28:25.277 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 28 11:28:25.277 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 11:28:25.277 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 11:28:25.277 INFO [stderr] 
Nov 28 11:28:25.277 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 11:28:25.277 INFO [stderr]    --> src/main.rs:137:17
Nov 28 11:28:25.277 INFO [stderr]     |
Nov 28 11:28:25.277 INFO [stderr] 137 |                 writeln!(output_file, "0{:0>15b}", address_value);
Nov 28 11:28:25.277 INFO [stderr]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 28 11:28:25.277 INFO [stderr]     |
Nov 28 11:28:25.277 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 11:28:25.277 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 11:28:25.277 INFO [stderr] 
Nov 28 11:28:25.277 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 11:28:25.277 INFO [stderr]    --> src/main.rs:140:17
Nov 28 11:28:25.277 INFO [stderr]     |
Nov 28 11:28:25.277 INFO [stderr] 140 | /                 writeln!(output_file, "111{}{}{}", 
Nov 28 11:28:25.277 INFO [stderr] 141 | |                          operation.get_machine_code_string(),
Nov 28 11:28:25.277 INFO [stderr] 142 | |                          destination.get_machine_code_string(), 
Nov 28 11:28:25.277 INFO [stderr] 143 | |                          jump.get_machine_code_string());
Nov 28 11:28:25.277 INFO [stderr]     | |_________________________________________________________^
Nov 28 11:28:25.277 INFO [stderr]     |
Nov 28 11:28:25.277 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 11:28:25.277 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 11:28:25.277 INFO [stderr] 
Nov 28 11:28:25.718 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 11:28:25.718 INFO [stderr]    --> src/main.rs:128:17
Nov 28 11:28:25.718 INFO [stderr]     |
Nov 28 11:28:25.718 INFO [stderr] 128 |                 writeln!(output_file, "0{:0>15b}", value);
Nov 28 11:28:25.718 INFO [stderr]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 28 11:28:25.718 INFO [stderr]     |
Nov 28 11:28:25.718 INFO [stderr]     = note: #[warn(unused_must_use)] on by default
Nov 28 11:28:25.718 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 11:28:25.718 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 11:28:25.718 INFO [stderr] 
Nov 28 11:28:25.718 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 11:28:25.718 INFO [stderr]    --> src/main.rs:137:17
Nov 28 11:28:25.718 INFO [stderr]     |
Nov 28 11:28:25.718 INFO [stderr] 137 |                 writeln!(output_file, "0{:0>15b}", address_value);
Nov 28 11:28:25.718 INFO [stderr]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 28 11:28:25.718 INFO [stderr]     |
Nov 28 11:28:25.718 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 11:28:25.718 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 11:28:25.718 INFO [stderr] 
Nov 28 11:28:25.720 INFO [stderr] warning: unused `std::result::Result` that must be used
Nov 28 11:28:25.720 INFO [stderr]    --> src/main.rs:140:17
Nov 28 11:28:25.720 INFO [stderr]     |
Nov 28 11:28:25.720 INFO [stderr] 140 | /                 writeln!(output_file, "111{}{}{}", 
Nov 28 11:28:25.720 INFO [stderr] 141 | |                          operation.get_machine_code_string(),
Nov 28 11:28:25.720 INFO [stderr] 142 | |                          destination.get_machine_code_string(), 
Nov 28 11:28:25.720 INFO [stderr] 143 | |                          jump.get_machine_code_string());
Nov 28 11:28:25.720 INFO [stderr]     | |_________________________________________________________^
Nov 28 11:28:25.720 INFO [stderr]     |
Nov 28 11:28:25.720 INFO [stderr]     = note: this `Result` may be an `Err` variant, which should be handled
Nov 28 11:28:25.720 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 11:28:25.720 INFO [stderr] 
Nov 28 11:28:25.756 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.86s
Nov 28 11:28:25.760 INFO [stderr] su: No module specific data is present
Nov 28 11:28:26.843 INFO running `"docker" "inspect" "374fe6a2bc4b660dd76ac992e55105db3ca73c7b38a8844bc9060eb52e26430f"`
Nov 28 11:28:27.180 INFO running `"docker" "rm" "-f" "374fe6a2bc4b660dd76ac992e55105db3ca73c7b38a8844bc9060eb52e26430f"`
Nov 28 11:28:27.526 INFO [stdout] 374fe6a2bc4b660dd76ac992e55105db3ca73c7b38a8844bc9060eb52e26430f