[INFO] fetching crate saberrs 0.3.1...
[INFO] checking saberrs-0.3.1 against try#a7a572ce3edd6d476191fbfe92c9c1986e009b34 for pr-87190-3
[INFO] extracting crate saberrs 0.3.1 into /workspace/builds/worker-3/source
[INFO] validating manifest of crates.io crate saberrs 0.3.1 on toolchain a7a572ce3edd6d476191fbfe92c9c1986e009b34
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate saberrs 0.3.1
[INFO] finished tweaking crates.io crate saberrs 0.3.1
[INFO] tweaked toml for crates.io crate saberrs 0.3.1 written to /workspace/builds/worker-3/source/Cargo.toml
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update", kill_on_drop: false }`
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:34b6a614d2c27851fe6cbf88fbd1137609cefab8b10d0615aaeb6fd47975d74e" "/opt/rustwide/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] fe5f56523c33aff2dabfeb66c77164327f4f93a22ee1f8f51ec9b7b7cf90b907
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] running `Command { std: "docker" "start" "-a" "fe5f56523c33aff2dabfeb66c77164327f4f93a22ee1f8f51ec9b7b7cf90b907", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "fe5f56523c33aff2dabfeb66c77164327f4f93a22ee1f8f51ec9b7b7cf90b907", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "fe5f56523c33aff2dabfeb66c77164327f4f93a22ee1f8f51ec9b7b7cf90b907", kill_on_drop: false }`
[INFO] [stdout] fe5f56523c33aff2dabfeb66c77164327f4f93a22ee1f8f51ec9b7b7cf90b907
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:34b6a614d2c27851fe6cbf88fbd1137609cefab8b10d0615aaeb6fd47975d74e" "/opt/rustwide/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 2f75f50665a018177cab007bc6aec78eec3e8ff61469914410b266eb53e984c9
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] running `Command { std: "docker" "start" "-a" "2f75f50665a018177cab007bc6aec78eec3e8ff61469914410b266eb53e984c9", kill_on_drop: false }`
[INFO] [stderr] Copying to /tmp/fixit
[INFO] [stderr] Running `cargo fix --edition`
[INFO] [stderr] note: Switching to Edition 2021 will enable the use of the version 2 feature resolver in Cargo.
[INFO] [stderr] This may cause some dependencies to be built with fewer features enabled than previously.
[INFO] [stderr] More information about the resolver changes may be found at https://doc.rust-lang.org/nightly/edition-guide/rust-2021/default-cargo-resolver.html
[INFO] [stderr] When building the following dependencies, the given features will no longer be used:
[INFO] [stderr] 
[INFO] [stderr]   libc v0.2.100: use_std
[INFO] [stderr] 
[INFO] [stderr]    Compiling libc v0.2.100
[INFO] [stderr]    Compiling nix v0.14.1
[INFO] [stderr]     Checking bitflags v1.3.2
[INFO] [stderr]     Checking cfg-if v1.0.0
[INFO] [stderr]     Checking log v0.4.14
[INFO] [stderr]     Checking serialport v3.3.0
[INFO] [stderr]     Checking saberrs v0.3.1 (/tmp/fixit)
[INFO] [stderr]    Migrating src/lib.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/test_packet.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/test_text.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/test_device.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/test_lib.rs from 2018 edition to 2021
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `test_packet`
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/utils/mod.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: multiple unused formatting arguments
[INFO] [stderr]    --> tests/utils/mod.rs:134:36
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", "{}", "{}", "{}", "{}", "{}", "{}", "{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ----        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ argument never used
[INFO] [stderr]     |                        |           |     |     |     |     |     |
[INFO] [stderr]     |                        |           |     |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     argument never used
[INFO] [stderr]     |                        |           |     argument never used
[INFO] [stderr]     |                        |           argument never used
[INFO] [stderr]     |                        multiple missing formatting specifiers
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_packet.rs:151:9
[INFO] [stderr]     |
[INFO] [stderr] 151 |         test_get_method!(saberchecksum, get_speed, vectors, responder);
[INFO] [stderr]     |         ---------------------------------------------------------------
[INFO] [stderr]     |         |
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: multiple unused formatting arguments
[INFO] [stderr]    --> tests/utils/mod.rs:134:36
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", "{}", "{}", "{}", "{}", "{}", "{}", "{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ----        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ argument never used
[INFO] [stderr]     |                        |           |     |     |     |     |     |
[INFO] [stderr]     |                        |           |     |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     argument never used
[INFO] [stderr]     |                        |           |     argument never used
[INFO] [stderr]     |                        |           argument never used
[INFO] [stderr]     |                        multiple missing formatting specifiers
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_packet.rs:165:9
[INFO] [stderr]     |
[INFO] [stderr] 165 |         test_get_method!(saberchecksum, get_voltage, vectors, responder);
[INFO] [stderr]     |         -----------------------------------------------------------------
[INFO] [stderr]     |         |
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: multiple unused formatting arguments
[INFO] [stderr]    --> tests/utils/mod.rs:134:36
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", "{}", "{}", "{}", "{}", "{}", "{}", "{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ----        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ argument never used
[INFO] [stderr]     |                        |           |     |     |     |     |     |
[INFO] [stderr]     |                        |           |     |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     argument never used
[INFO] [stderr]     |                        |           |     argument never used
[INFO] [stderr]     |                        |           argument never used
[INFO] [stderr]     |                        multiple missing formatting specifiers
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_packet.rs:179:9
[INFO] [stderr]     |
[INFO] [stderr] 179 |         test_get_method!(saberchecksum, get_current, vectors, responder);
[INFO] [stderr]     |         -----------------------------------------------------------------
[INFO] [stderr]     |         |
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: multiple unused formatting arguments
[INFO] [stderr]    --> tests/utils/mod.rs:134:36
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", "{}", "{}", "{}", "{}", "{}", "{}", "{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ----        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ argument never used
[INFO] [stderr]     |                        |           |     |     |     |     |     |
[INFO] [stderr]     |                        |           |     |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     argument never used
[INFO] [stderr]     |                        |           |     argument never used
[INFO] [stderr]     |                        |           argument never used
[INFO] [stderr]     |                        multiple missing formatting specifiers
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_packet.rs:193:9
[INFO] [stderr]     |
[INFO] [stderr] 193 |         test_get_method!(saberchecksum, get_temperature, vectors, responder);
[INFO] [stderr]     |         ---------------------------------------------------------------------
[INFO] [stderr]     |         |
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: multiple unused formatting arguments
[INFO] [stderr]    --> tests/utils/mod.rs:134:36
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", "{}", "{}", "{}", "{}", "{}", "{}", "{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ----        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ argument never used
[INFO] [stderr]     |                        |           |     |     |     |     |     |
[INFO] [stderr]     |                        |           |     |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     argument never used
[INFO] [stderr]     |                        |           |     argument never used
[INFO] [stderr]     |                        |           argument never used
[INFO] [stderr]     |                        multiple missing formatting specifiers
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_packet.rs:335:9
[INFO] [stderr]     |
[INFO] [stderr] 335 |         test_get_method!(sabercrc, get_speed, vectors, responder);
[INFO] [stderr]     |         ----------------------------------------------------------
[INFO] [stderr]     |         |
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: multiple unused formatting arguments
[INFO] [stderr]    --> tests/utils/mod.rs:134:36
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", "{}", "{}", "{}", "{}", "{}", "{}", "{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ----        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ argument never used
[INFO] [stderr]     |                        |           |     |     |     |     |     |
[INFO] [stderr]     |                        |           |     |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     argument never used
[INFO] [stderr]     |                        |           |     argument never used
[INFO] [stderr]     |                        |           argument never used
[INFO] [stderr]     |                        multiple missing formatting specifiers
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_packet.rs:349:9
[INFO] [stderr]     |
[INFO] [stderr] 349 |         test_get_method!(sabercrc, get_voltage, vectors, responder);
[INFO] [stderr]     |         ------------------------------------------------------------
[INFO] [stderr]     |         |
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: multiple unused formatting arguments
[INFO] [stderr]    --> tests/utils/mod.rs:134:36
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", "{}", "{}", "{}", "{}", "{}", "{}", "{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ----        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ argument never used
[INFO] [stderr]     |                        |           |     |     |     |     |     |
[INFO] [stderr]     |                        |           |     |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     argument never used
[INFO] [stderr]     |                        |           |     argument never used
[INFO] [stderr]     |                        |           argument never used
[INFO] [stderr]     |                        multiple missing formatting specifiers
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_packet.rs:363:9
[INFO] [stderr]     |
[INFO] [stderr] 363 |         test_get_method!(sabercrc, get_current, vectors, responder);
[INFO] [stderr]     |         ------------------------------------------------------------
[INFO] [stderr]     |         |
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: multiple unused formatting arguments
[INFO] [stderr]    --> tests/utils/mod.rs:134:36
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", "{}", "{}", "{}", "{}", "{}", "{}", "{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ----        ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ argument never used
[INFO] [stderr]     |                        |           |     |     |     |     |     |
[INFO] [stderr]     |                        |           |     |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     |     argument never used
[INFO] [stderr]     |                        |           |     |     argument never used
[INFO] [stderr]     |                        |           |     argument never used
[INFO] [stderr]     |                        |           argument never used
[INFO] [stderr]     |                        multiple missing formatting specifiers
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_packet.rs:377:9
[INFO] [stderr]     |
[INFO] [stderr] 377 |         test_get_method!(sabercrc, get_temperature, vectors, responder);
[INFO] [stderr]     |         ----------------------------------------------------------------
[INFO] [stderr]     |         |
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |         in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 8 previous errors
[INFO] [stderr] 
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> tests/utils/responder.rs:85:20
[INFO] [stdout]    |
[INFO] [stdout] 85 |               panic!(format!(
[INFO] [stdout]    |  ____________________^
[INFO] [stdout] 86 | |                 "Expected {:#02x} ({:?}) but received {:#02x} ({:?})",
[INFO] [stdout] 87 | |                 expected_byte, expected_byte as char, received, received as char
[INFO] [stdout] 88 | |             ))
[INFO] [stdout]    | |_____________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `--force-warn non-fmt-panics` implied by `--force-warn rust-2021-compatibility`
[INFO] [stdout]    = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the panic!() macro supports formatting, so there's no need for the format!() macro here
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 85 ~             panic!(
[INFO] [stdout] 86 |                 "Expected {:#02x} ({:?}) but received {:#02x} ({:?})",
[INFO] [stdout] 87 |                 expected_byte, expected_byte as char, received, received as char
[INFO] [stdout] 88 ~             )
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:144:5
[INFO] [stdout]     |
[INFO] [stdout] 144 |     test_get_method!(sabertext, get_speed, vectors, responder);
[INFO] [stdout]     |     ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:157:5
[INFO] [stdout]     |
[INFO] [stdout] 157 |     test_get_method!(sabertext, get_power, vectors, responder);
[INFO] [stdout]     |     ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:170:5
[INFO] [stdout]     |
[INFO] [stdout] 170 |     test_get_method!(sabertext, get_voltage, vectors, responder);
[INFO] [stdout]     |     ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:183:5
[INFO] [stdout]     |
[INFO] [stdout] 183 |     test_get_method!(sabertext, get_current, vectors, responder);
[INFO] [stdout]     |     ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:196:5
[INFO] [stdout]     |
[INFO] [stdout] 196 |     test_get_method!(sabertext, get_temperature, vectors, responder);
[INFO] [stdout]     |     ----------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 6 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> tests/utils/responder.rs:85:20
[INFO] [stdout]    |
[INFO] [stdout] 85 |               panic!(format!(
[INFO] [stdout]    |  ____________________^
[INFO] [stdout] 86 | |                 "Expected {:#02x} ({:?}) but received {:#02x} ({:?})",
[INFO] [stdout] 87 | |                 expected_byte, expected_byte as char, received, received as char
[INFO] [stdout] 88 | |             ))
[INFO] [stdout]    | |_____________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `--force-warn non-fmt-panics` implied by `--force-warn rust-2021-compatibility`
[INFO] [stdout]    = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the panic!() macro supports formatting, so there's no need for the format!() macro here
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 85 ~             panic!(
[INFO] [stdout] 86 |                 "Expected {:#02x} ({:?}) but received {:#02x} ({:?})",
[INFO] [stdout] 87 |                 expected_byte, expected_byte as char, received, received as char
[INFO] [stdout] 88 ~             )
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:151:9
[INFO] [stdout]     |
[INFO] [stdout] 151 |         test_get_method!(saberchecksum, get_speed, vectors, responder);
[INFO] [stdout]     |         --------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:165:9
[INFO] [stdout]     |
[INFO] [stdout] 165 |         test_get_method!(saberchecksum, get_voltage, vectors, responder);
[INFO] [stdout]     |         ----------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:179:9
[INFO] [stdout]     |
[INFO] [stdout] 179 |         test_get_method!(saberchecksum, get_current, vectors, responder);
[INFO] [stdout]     |         ----------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:193:9
[INFO] [stdout]     |
[INFO] [stdout] 193 |         test_get_method!(saberchecksum, get_temperature, vectors, responder);
[INFO] [stdout]     |         --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:335:9
[INFO] [stdout]     |
[INFO] [stdout] 335 |         test_get_method!(sabercrc, get_speed, vectors, responder);
[INFO] [stdout]     |         ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:349:9
[INFO] [stdout]     |
[INFO] [stdout] 349 |         test_get_method!(sabercrc, get_voltage, vectors, responder);
[INFO] [stdout]     |         ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:363:9
[INFO] [stdout]     |
[INFO] [stdout] 363 |         test_get_method!(sabercrc, get_current, vectors, responder);
[INFO] [stdout]     |         ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:377:9
[INFO] [stdout]     |
[INFO] [stdout] 377 |         test_get_method!(sabercrc, get_temperature, vectors, responder);
[INFO] [stdout]     |         ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of panic!() is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: add a "{}" format string to Display the message
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 9 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]        Fixed tests/utils/responder.rs (1 fix)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 7.98s
[INFO] [stderr] Running `cargo check` to verify 2021
[INFO] [stderr]    Compiling libc v0.2.100
[INFO] [stderr]     Checking nix v0.14.1
[INFO] [stderr]     Checking serialport v3.3.0
[INFO] [stderr]     Checking saberrs v0.3.1 (/tmp/fixit)
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:144:5
[INFO] [stdout]     |
[INFO] [stdout] 144 |     test_get_method!(sabertext, get_speed, vectors, responder);
[INFO] [stdout]     |     ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:157:5
[INFO] [stdout]     |
[INFO] [stdout] 157 |     test_get_method!(sabertext, get_power, vectors, responder);
[INFO] [stdout]     |     ----------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:170:5
[INFO] [stdout]     |
[INFO] [stdout] 170 |     test_get_method!(sabertext, get_voltage, vectors, responder);
[INFO] [stdout]     |     ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:183:5
[INFO] [stdout]     |
[INFO] [stdout] 183 |     test_get_method!(sabertext, get_current, vectors, responder);
[INFO] [stdout]     |     ------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_text.rs:196:5
[INFO] [stdout]     |
[INFO] [stdout] 196 |     test_get_method!(sabertext, get_temperature, vectors, responder);
[INFO] [stdout]     |     ----------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:151:9
[INFO] [stdout]     |
[INFO] [stdout] 151 |         test_get_method!(saberchecksum, get_speed, vectors, responder);
[INFO] [stdout]     |         --------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:165:9
[INFO] [stdout]     |
[INFO] [stdout] 165 |         test_get_method!(saberchecksum, get_voltage, vectors, responder);
[INFO] [stdout]     |         ----------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:179:9
[INFO] [stdout]     |
[INFO] [stdout] 179 |         test_get_method!(saberchecksum, get_current, vectors, responder);
[INFO] [stdout]     |         ----------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:193:9
[INFO] [stdout]     |
[INFO] [stdout] 193 |         test_get_method!(saberchecksum, get_temperature, vectors, responder);
[INFO] [stdout]     |         --------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:335:9
[INFO] [stdout]     |
[INFO] [stdout] 335 |         test_get_method!(sabercrc, get_speed, vectors, responder);
[INFO] [stdout]     |         ---------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:349:9
[INFO] [stdout]     |
[INFO] [stdout] 349 |         test_get_method!(sabercrc, get_voltage, vectors, responder);
[INFO] [stdout]     |         ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:363:9
[INFO] [stdout]     |
[INFO] [stdout] 363 |         test_get_method!(sabercrc, get_current, vectors, responder);
[INFO] [stdout]     |         ------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: format argument must be a string literal
[INFO] [stdout]    --> tests/utils/mod.rs:134:24
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: tests/test_packet.rs:377:9
[INFO] [stdout]     |
[INFO] [stdout] 377 |         test_get_method!(sabercrc, get_temperature, vectors, responder);
[INFO] [stdout]     |         ---------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: you might be missing a string literal to format with
[INFO] [stdout]     |
[INFO] [stdout] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stdout]     |                        +++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 5 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `saberrs` due to 6 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: aborting due to 8 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: build failed
[INFO] [stderr] error: failed to check after updating to 2021
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   process didn't exit successfully: `cargo check --frozen --all --all-targets --message-format=json` (exit status: 101)
[INFO] running `Command { std: "docker" "inspect" "2f75f50665a018177cab007bc6aec78eec3e8ff61469914410b266eb53e984c9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "2f75f50665a018177cab007bc6aec78eec3e8ff61469914410b266eb53e984c9", kill_on_drop: false }`
[INFO] [stdout] 2f75f50665a018177cab007bc6aec78eec3e8ff61469914410b266eb53e984c9