[INFO] fetching crate saberrs 0.3.1...
[INFO] checking saberrs-0.3.1 against master#ab869e094a907cc5d19b4080f22eccaf347f1f95 for pr-129604
[INFO] extracting crate saberrs 0.3.1 into /workspace/builds/worker-2-tc1/source
[INFO] validating manifest of crates.io crate saberrs 0.3.1 on toolchain ab869e094a907cc5d19b4080f22eccaf347f1f95
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "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-2-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 22 packages to latest compatible versions
[INFO] [stderr]       Adding bitflags v1.3.2 (latest: v2.6.0)
[INFO] [stderr]       Adding cfg-if v0.1.10 (latest: v1.0.0)
[INFO] [stderr]       Adding mach v0.1.2 (latest: v0.3.2)
[INFO] [stderr]       Adding mach v0.2.3 (latest: v0.3.2)
[INFO] [stderr]       Adding nix v0.14.1 (latest: v0.29.0)
[INFO] [stderr]       Adding serialport v3.3.0 (latest: v4.5.0)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/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:923055f121b5182466d55868a8b05e67af8ba4a3a3f6bad814e953ca3cd3ac2a" "/opt/rustwide/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 62b7ca8f7fce3bd32c7fe198838b372116d505438c954a30577caf29f03f8a8f
[INFO] running `Command { std: "docker" "start" "-a" "62b7ca8f7fce3bd32c7fe198838b372116d505438c954a30577caf29f03f8a8f", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "62b7ca8f7fce3bd32c7fe198838b372116d505438c954a30577caf29f03f8a8f", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "62b7ca8f7fce3bd32c7fe198838b372116d505438c954a30577caf29f03f8a8f", kill_on_drop: false }`
[INFO] [stdout] 62b7ca8f7fce3bd32c7fe198838b372116d505438c954a30577caf29f03f8a8f
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/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" "RUSTDOCFLAGS=--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:923055f121b5182466d55868a8b05e67af8ba4a3a3f6bad814e953ca3cd3ac2a" "/opt/rustwide/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 494fa9ee536f868b470d6f734d2a387606759f53b5acebe59d6e4375f4cfbaeb
[INFO] running `Command { std: "docker" "start" "-a" "494fa9ee536f868b470d6f734d2a387606759f53b5acebe59d6e4375f4cfbaeb", kill_on_drop: false }`
[INFO] [stderr]    Compiling libc v0.2.158
[INFO] [stderr]    Compiling nix v0.14.1
[INFO] [stderr]     Checking void v1.0.2
[INFO] [stderr]     Checking bitflags v1.3.2
[INFO] [stderr]     Checking cfg-if v0.1.10
[INFO] [stderr]     Checking serialport v3.3.0
[INFO] [stderr]     Checking saberrs v0.3.1 (/opt/rustwide/workdir)
[INFO] [stdout] warning: field `0` is never read
[INFO] [stdout]   --> src/error.rs:34:8
[INFO] [stdout]    |
[INFO] [stdout] 34 |     Io(io::Error),
[INFO] [stdout]    |     -- ^^^^^^^^^
[INFO] [stdout]    |     |
[INFO] [stdout]    |     field in this variant
[INFO] [stdout]    |
[INFO] [stdout]    = note: `SubError` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis
[INFO] [stdout]    = note: `#[warn(dead_code)]` on by default
[INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
[INFO] [stdout]    |
[INFO] [stdout] 34 |     Io(()),
[INFO] [stdout]    |        ~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 1 warning emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: field `0` is never read
[INFO] [stdout]   --> src/error.rs:34:8
[INFO] [stdout]    |
[INFO] [stdout] 34 |     Io(io::Error),
[INFO] [stdout]    |     -- ^^^^^^^^^
[INFO] [stdout]    |     |
[INFO] [stdout]    |     field in this variant
[INFO] [stdout]    |
[INFO] [stdout]    = note: `SubError` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis
[INFO] [stdout]    = note: `#[warn(dead_code)]` on by default
[INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
[INFO] [stdout]    |
[INFO] [stdout] 34 |     Io(()),
[INFO] [stdout]    |        ~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 1 warning 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: 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]    = note: `#[warn(non_fmt_panics)]` on by default
[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: 1 warning 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: 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]    = note: `#[warn(non_fmt_panics)]` on by default
[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: 1 warning emitted
[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: `#[warn(non_fmt_panics)]` on by default
[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: 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: 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: 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: 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]    = note: `#[warn(non_fmt_panics)]` on by default
[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]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 5.06s
[INFO] running `Command { std: "docker" "inspect" "494fa9ee536f868b470d6f734d2a387606759f53b5acebe59d6e4375f4cfbaeb", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "494fa9ee536f868b470d6f734d2a387606759f53b5acebe59d6e4375f4cfbaeb", kill_on_drop: false }`
[INFO] [stdout] 494fa9ee536f868b470d6f734d2a387606759f53b5acebe59d6e4375f4cfbaeb