[INFO] fetching crate saberrs 0.3.1...
[INFO] testing saberrs-0.3.1 against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0
[INFO] extracting crate saberrs 0.3.1 into /workspace/builds/worker-3-tc1/source
[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-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate saberrs 0.3.1 on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 21 packages to latest compatible versions
[INFO] [stderr]       Adding serialport v3.3.0 (available: v4.7.2)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded mach v0.2.3
[INFO] [stderr]   Downloaded serialport v3.3.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 3cd6c03a1259420acc4d3ab68a8751415ab6e4413895099a63853af539b42ec7
[INFO] running `Command { std: "docker" "start" "-a" "3cd6c03a1259420acc4d3ab68a8751415ab6e4413895099a63853af539b42ec7", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "3cd6c03a1259420acc4d3ab68a8751415ab6e4413895099a63853af539b42ec7", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "3cd6c03a1259420acc4d3ab68a8751415ab6e4413895099a63853af539b42ec7", kill_on_drop: false }`
[INFO] [stdout] 3cd6c03a1259420acc4d3ab68a8751415ab6e4413895099a63853af539b42ec7
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "build" "--frozen" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }`
[INFO] [stdout] f749cfb2aa6b4def43afc5fb75b88ecf4e959097b7f340ed614a3046086c559f
[INFO] running `Command { std: "docker" "start" "-a" "f749cfb2aa6b4def43afc5fb75b88ecf4e959097b7f340ed614a3046086c559f", kill_on_drop: false }`
[INFO] [stderr]    Compiling libc v0.2.174
[INFO] [stderr]    Compiling nix v0.14.1
[INFO] [stderr]    Compiling log v0.4.27
[INFO] [stderr]    Compiling serialport v3.3.0
[INFO] [stderr]    Compiling 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(io::Error),
[INFO] [stdout] 34 +     Io(()),
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 5.57s
[INFO] running `Command { std: "docker" "inspect" "f749cfb2aa6b4def43afc5fb75b88ecf4e959097b7f340ed614a3046086c559f", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f749cfb2aa6b4def43afc5fb75b88ecf4e959097b7f340ed614a3046086c559f", kill_on_drop: false }`
[INFO] [stdout] f749cfb2aa6b4def43afc5fb75b88ecf4e959097b7f340ed614a3046086c559f
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--no-run" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }`
[INFO] [stdout] 81983c1f52efde13836ffcb2be6d6e9491cca9c0f9f3127b9e5df21a506a186a
[INFO] running `Command { std: "docker" "start" "-a" "81983c1f52efde13836ffcb2be6d6e9491cca9c0f9f3127b9e5df21a506a186a", kill_on_drop: false }`
[INFO] [stderr]    Compiling 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(io::Error),
[INFO] [stdout] 34 +     Io(()),
[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]    = 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_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: 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/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: 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(io::Error),
[INFO] [stdout] 34 +     Io(()),
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 1.76s
[INFO] running `Command { std: "docker" "inspect" "81983c1f52efde13836ffcb2be6d6e9491cca9c0f9f3127b9e5df21a506a186a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "81983c1f52efde13836ffcb2be6d6e9491cca9c0f9f3127b9e5df21a506a186a", kill_on_drop: false }`
[INFO] [stdout] 81983c1f52efde13836ffcb2be6d6e9491cca9c0f9f3127b9e5df21a506a186a
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }`
[INFO] [stdout] 002b399f4358ee8d15fd979b4a476ca69580454126ce278618dea976f4c44387
[INFO] running `Command { std: "docker" "start" "-a" "002b399f4358ee8d15fd979b4a476ca69580454126ce278618dea976f4c44387", kill_on_drop: false }`
[INFO] [stderr] warning: field `0` is never read
[INFO] [stderr]   --> src/error.rs:34:8
[INFO] [stderr]    |
[INFO] [stderr] 34 |     Io(io::Error),
[INFO] [stderr]    |     -- ^^^^^^^^^
[INFO] [stderr]    |     |
[INFO] [stderr]    |     field in this variant
[INFO] [stderr]    |
[INFO] [stderr]    = note: `SubError` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis
[INFO] [stderr]    = note: `#[warn(dead_code)]` on by default
[INFO] [stderr] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
[INFO] [stderr]    |
[INFO] [stderr] 34 -     Io(io::Error),
[INFO] [stderr] 34 +     Io(()),
[INFO] [stderr]    |
[INFO] [stderr] 
[INFO] [stderr] warning: `saberrs` (lib) generated 1 warning
[INFO] [stderr] warning: `saberrs` (lib test) generated 1 warning (1 duplicate)
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]   --> tests/utils/responder.rs:85:20
[INFO] [stderr]    |
[INFO] [stderr] 85 |               panic!(format!(
[INFO] [stderr]    |  ____________________^
[INFO] [stderr] 86 | |                 "Expected {:#02x} ({:?}) but received {:#02x} ({:?})",
[INFO] [stderr] 87 | |                 expected_byte, expected_byte as char, received, received as char
[INFO] [stderr] 88 | |             ))
[INFO] [stderr]    | |_____________^
[INFO] [stderr]    |
[INFO] [stderr]    = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]    = note: the `panic!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]    = note: `#[warn(non_fmt_panics)]` on by default
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]    |
[INFO] [stderr] 85 ~             panic!(
[INFO] [stderr] 86 |                 "Expected {:#02x} ({:?}) but received {:#02x} ({:?})",
[INFO] [stderr] 87 |                 expected_byte, expected_byte as char, received, received as char
[INFO] [stderr] 88 ~             )
[INFO] [stderr]    |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[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]     |         -------------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[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]     |         ---------------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[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]     |         ---------------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[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]     |         -------------------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[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]     |         --------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[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]     |         ----------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[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]     |         ----------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[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]     |         --------------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_text.rs:144:5
[INFO] [stderr]     |
[INFO] [stderr] 144 |     test_get_method!(sabertext, get_speed, vectors, responder);
[INFO] [stderr]     |     ---------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: `#[warn(non_fmt_panics)]` on by default
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_text.rs:157:5
[INFO] [stderr]     |
[INFO] [stderr] 157 |     test_get_method!(sabertext, get_power, vectors, responder);
[INFO] [stderr]     |     ---------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_text.rs:170:5
[INFO] [stderr]     |
[INFO] [stderr] 170 |     test_get_method!(sabertext, get_voltage, vectors, responder);
[INFO] [stderr]     |     ------------------------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_text.rs:183:5
[INFO] [stderr]     |
[INFO] [stderr] 183 |     test_get_method!(sabertext, get_current, vectors, responder);
[INFO] [stderr]     |     ------------------------------------------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> tests/utils/mod.rs:134:24
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!($responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: tests/test_text.rs:196:5
[INFO] [stderr]     |
[INFO] [stderr] 196 |     test_get_method!(sabertext, get_temperature, vectors, responder);
[INFO] [stderr]     |     ---------------------------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: this warning originates in the macro `test_get_method` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: add a "{}" format string to `Display` the message
[INFO] [stderr]     |
[INFO] [stderr] 134 |                 panic!("{}", $responder.join_panic().unwrap_err());
[INFO] [stderr]     |                        +++++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]   --> tests/utils/responder.rs:85:20
[INFO] [stderr]    |
[INFO] [stderr] 85 |               panic!(format!(
[INFO] [stderr]    |  ____________________^
[INFO] [stderr] 86 | |                 "Expected {:#02x} ({:?}) but received {:#02x} ({:?})",
[INFO] [stderr] 87 | |                 expected_byte, expected_byte as char, received, received as char
[INFO] [stderr] 88 | |             ))
[INFO] [stderr]    | |_____________^
[INFO] [stderr]    |
[INFO] [stderr]    = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]    = note: the `panic!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]    |
[INFO] [stderr] 85 ~             panic!(
[INFO] [stderr] 86 |                 "Expected {:#02x} ({:?}) but received {:#02x} ({:?})",
[INFO] [stderr] 87 |                 expected_byte, expected_byte as char, received, received as char
[INFO] [stderr] 88 ~             )
[INFO] [stderr]    |
[INFO] [stderr] 
[INFO] [stderr] warning: `saberrs` (test "test_device") generated 1 warning (run `cargo fix --test "test_device"` to apply 1 suggestion)
[INFO] [stderr] warning: `saberrs` (test "test_lib") generated 1 warning (1 duplicate)
[INFO] [stderr] warning: `saberrs` (test "test_packet") generated 9 warnings (1 duplicate) (run `cargo fix --test "test_packet"` to apply 8 suggestions)
[INFO] [stderr] warning: `saberrs` (test "test_text") generated 6 warnings (run `cargo fix --test "test_text"` to apply 6 suggestions)
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.06s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/saberrs-482b8a15d7d0458e)
[INFO] [stdout] 
[INFO] [stderr]      Running tests/test_device.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/test_device-bf5810429b1b1d5d)
[INFO] [stdout] running 5 tests
[INFO] [stdout] test sabertooth2x32::packetserial::checksum::tests::test_checksum ... ok
[INFO] [stdout] test sabertooth2x32::packetserial::crc::tests::test_crc14 ... ok
[INFO] [stdout] test sabertooth2x32::packetserial::crc::tests::test_crc7 ... ok
[INFO] [stdout] test sabertooth2x32::packetserial::crc::tests::test_crc_packet ... ok
[INFO] [stdout] test sabertooth2x32::plaintext::tests::test_split_response ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] running 5 tests
[INFO] [stdout] test timeout_setting ... ok
[INFO] [stdout] test read_with_device ... ok
[INFO] [stdout] test write_with_device ... ok
[INFO] [stdout] test timeout_default_setting ... ok
[INFO] [stdout] test timeout_actual ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.16s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/test_lib.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/test_lib-1907367154218cc5)
[INFO] [stdout] 
[INFO] [stdout] running 1 test
[INFO] [stdout] test instantiate_multiple_protocols ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/test_packet.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/test_packet-2c5b1afd9b273b2c)
[INFO] [stdout] 
[INFO] [stdout] running 26 tests
[INFO] [stdout] test checksum::set_ramp ... ok
[INFO] [stdout] test checksum::set_aux ... ok
[INFO] [stdout] test checksum::set_speed_errs ... ok
[INFO] [stdout] test checksum::set_turn ... ok
[INFO] [stdout] test checksum::set_speed ... ok
[INFO] [stdout] test crc::set_aux ... ok
[INFO] [stdout] test checksum::shutdown ... ok
[INFO] [stdout] test crc::set_drive ... ok
[INFO] [stdout] test crc::set_ramp ... ok
[INFO] [stdout] test checksum::startup ... ok
[INFO] [stdout] test crc::set_speed ... ok
[INFO] [stdout] test crc::set_power ... ok
[INFO] [stdout] test checksum::set_power ... ok
[INFO] [stdout] test crc::set_turn ... ok
[INFO] [stdout] test crc::set_speed_errs ... ok
[INFO] [stdout] test crc::startup ... ok
[INFO] [stdout] test crc::shutdown ... ok
[INFO] [stdout] test checksum::set_drive ... ok
[INFO] [stdout] test crc::get_current ... ok
[INFO] [stdout] test crc::get_voltage ... ok
[INFO] [stdout] test crc::get_temperature ... ok
[INFO] [stdout] test checksum::get_speed ... ok
[INFO] [stdout] test crc::get_speed ... ok
[INFO] [stdout] test checksum::get_temperature ... ok
[INFO] [stdout] test checksum::get_voltage ... ok
[INFO] [stdout] test checksum::get_current ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 26 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.06s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/test_text.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/test_text-46827eafcba6d094)
[INFO] [stdout] 
[INFO] [stdout] running 15 tests
[INFO] [stdout] test set_drive ... ok
[INFO] [stdout] test set_speed_errs ... ok
[INFO] [stdout] test set_aux ... ok
[INFO] [stdout] test set_power ... ok
[INFO] [stdout] test set_ramp ... ok
[INFO] [stdout] test set_speed ... ok
[INFO] [stdout] test set_turn ... ok
[INFO] [stdout] test shutdown ... ok
[INFO] [stdout] test startup ... ok
[INFO] [stdout] test test_from_serialport ... ok
[INFO] [stdout] test get_temperature ... ok
[INFO] [stdout] test get_power ... ok
[INFO] [stdout] test get_voltage ... ok
[INFO] [stdout] test get_current ... ok
[INFO] [stdout] test get_speed ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 15 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.08s
[INFO] [stdout] 
[INFO] running `Command { std: "docker" "inspect" "002b399f4358ee8d15fd979b4a476ca69580454126ce278618dea976f4c44387", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "002b399f4358ee8d15fd979b4a476ca69580454126ce278618dea976f4c44387", kill_on_drop: false }`
[INFO] [stdout] 002b399f4358ee8d15fd979b4a476ca69580454126ce278618dea976f4c44387