[INFO] fetching crate core_cbc_casper 0.1.0...
[INFO] checking core_cbc_casper-0.1.0 against master#fffed276b51cf514622e8d3109d620501cc01670 for pr-134021
[INFO] extracting crate core_cbc_casper 0.1.0 into /workspace/builds/worker-2-tc1/source
[INFO] removed /workspace/builds/worker-2-tc1/source/rust-toolchain
[INFO] started tweaking crates.io crate core_cbc_casper 0.1.0
[INFO] finished tweaking crates.io crate core_cbc_casper 0.1.0
[INFO] tweaked toml for crates.io crate core_cbc_casper 0.1.0 written to /workspace/builds/worker-2-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate core_cbc_casper 0.1.0 on toolchain fffed276b51cf514622e8d3109d620501cc01670
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+fffed276b51cf514622e8d3109d620501cc01670" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate core_cbc_casper 0.1.0 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+fffed276b51cf514622e8d3109d620501cc01670" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded crypto-mac v0.5.2
[INFO] [stderr]   Downloaded blake2 v0.7.1
[INFO] [stderr]   Downloaded num-traits v0.2.9
[INFO] [stderr]   Downloaded itertools v0.8.1
[INFO] [stderr]   Downloaded proptest v0.9.4
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,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" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:3a6becf2bc8dde7f3fa57ede90e4f284e72d296796fc446bbb1e2c7cc0530151" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] c2d9fb05bf4f691f3e2af358a8676d0946d14dbcad423b3f34a585f248fb67bd
[INFO] running `Command { std: "docker" "start" "c2d9fb05bf4f691f3e2af358a8676d0946d14dbcad423b3f34a585f248fb67bd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "c2d9fb05bf4f691f3e2af358a8676d0946d14dbcad423b3f34a585f248fb67bd" "/opt/rustwide/cargo-home/bin/cargo" "+fffed276b51cf514622e8d3109d620501cc01670" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "c2d9fb05bf4f691f3e2af358a8676d0946d14dbcad423b3f34a585f248fb67bd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-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" "-w" "/opt/rustwide/workdir" "--user" "0:0" "c2d9fb05bf4f691f3e2af358a8676d0946d14dbcad423b3f34a585f248fb67bd" "/opt/rustwide/cargo-home/bin/cargo" "+fffed276b51cf514622e8d3109d620501cc01670" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stderr]    Compiling libc v0.2.65
[INFO] [stderr]    Compiling crossbeam-utils v0.7.0
[INFO] [stderr]    Compiling serde v1.0.102
[INFO] [stderr]    Compiling crossbeam-epoch v0.8.0
[INFO] [stderr]    Compiling proc-macro2 v1.0.6
[INFO] [stderr]    Compiling typenum v1.11.2
[INFO] [stderr]    Compiling memchr v2.2.1
[INFO] [stderr]    Compiling ryu v1.0.2
[INFO] [stderr]     Checking either v1.5.3
[INFO] [stderr]    Compiling rayon-core v1.7.0
[INFO] [stderr]    Compiling syn v1.0.8
[INFO] [stderr]    Compiling num-traits v0.2.9
[INFO] [stderr]    Compiling bincode v1.2.0
[INFO] [stderr]    Compiling memoffset v0.5.3
[INFO] [stderr]    Compiling cast v0.2.3
[INFO] [stderr]     Checking regex-automata v0.1.8
[INFO] [stderr]     Checking constant_time_eq v0.1.4
[INFO] [stderr]     Checking itertools v0.8.1
[INFO] [stderr]     Checking static_assertions v0.2.5
[INFO] [stderr]     Checking same-file v1.0.5
[INFO] [stderr]     Checking byte-tools v0.2.0
[INFO] [stderr]     Checking walkdir v2.2.9
[INFO] [stderr]     Checking rand_xoshiro v0.1.0
[INFO] [stderr]     Checking clap v2.33.0
[INFO] [stderr]     Checking itertools v0.7.11
[INFO] [stderr]     Checking num_cpus v1.11.1
[INFO] [stderr]     Checking fixed-hash v0.3.2
[INFO] [stderr]     Checking rand_os v0.1.3
[INFO] [stderr]     Checking atty v0.2.13
[INFO] [stderr]    Compiling quote v1.0.2
[INFO] [stderr]     Checking crossbeam-queue v0.2.0
[INFO] [stderr]     Checking criterion-plot v0.3.1
[INFO] [stderr]     Checking csv-core v0.1.6
[INFO] [stderr]     Checking crossbeam-deque v0.7.2
[INFO] [stderr]     Checking generic-array v0.9.0
[INFO] [stderr]     Checking rayon v1.3.0
[INFO] [stderr]     Checking digest v0.7.6
[INFO] [stderr]     Checking crypto-mac v0.5.2
[INFO] [stderr]     Checking blake2 v0.7.1
[INFO] [stderr]    Compiling serde_derive v1.0.102
[INFO] [stderr]     Checking serde_json v1.0.41
[INFO] [stderr]     Checking bstr v0.2.8
[INFO] [stderr]     Checking csv v1.1.1
[INFO] [stderr]     Checking tinytemplate v1.0.2
[INFO] [stderr]     Checking criterion v0.2.11
[INFO] [stderr]     Checking core_cbc_casper v0.1.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/tests_common/integer.rs:32:62
[INFO] [stdout]    |
[INFO] [stdout] 32 | #[derive(Clone, Eq, Debug, Ord, PartialOrd, PartialEq, Hash, serde_derive::Serialize)]
[INFO] [stdout]    |                                                              ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/tests_common/vote_count.rs:50:70
[INFO] [stdout]    |
[INFO] [stdout] 50 | #[derive(Clone, Copy, Eq, Ord, PartialOrd, PartialEq, Hash, Default, serde_derive::Serialize)]
[INFO] [stdout]    |                                                                      ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/blockchain.rs:81:45
[INFO] [stdout]    |
[INFO] [stdout] 81 | #[derive(Clone, Eq, PartialEq, Debug, Hash, Serialize)]
[INFO] [stdout]    |                                             ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `dev`
[INFO] [stdout]   --> src/util/hash.rs:21:1
[INFO] [stdout]    |
[INFO] [stdout] 21 | / fixed_hash::construct_fixed_hash!(
[INFO] [stdout] 22 | |     pub struct Hash(64);
[INFO] [stdout] 23 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fixed_hash::construct_fixed_hash` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fixed_hash::construct_fixed_hash` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: struct `Tx` is never constructed
[INFO] [stdout]   --> src/tests_common/integer.rs:49:12
[INFO] [stdout]    |
[INFO] [stdout] 49 | pub struct Tx;
[INFO] [stdout]    |            ^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/tests_common/integer.rs:32:62
[INFO] [stdout]    |
[INFO] [stdout] 32 | #[derive(Clone, Eq, Debug, Ord, PartialOrd, PartialEq, Hash, serde_derive::Serialize)]
[INFO] [stdout]    |                                                              ^----------------------
[INFO] [stdout]    |                                                              |
[INFO] [stdout]    |                                                              `Serialize` is not local
[INFO] [stdout]    |                                                              move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_IntegerWrapper`
[INFO] [stdout] 33 | pub struct IntegerWrapper(pub u32);
[INFO] [stdout]    |            -------------- `IntegerWrapper` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/tests_common/vote_count.rs:50:70
[INFO] [stdout]    |
[INFO] [stdout] 50 | #[derive(Clone, Copy, Eq, Ord, PartialOrd, PartialEq, Hash, Default, serde_derive::Serialize)]
[INFO] [stdout]    |                                                                      ^----------------------
[INFO] [stdout]    |                                                                      |
[INFO] [stdout]    |                                                                      `Serialize` is not local
[INFO] [stdout]    |                                                                      move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_VoteCount`
[INFO] [stdout] 51 | pub struct VoteCount {
[INFO] [stdout]    |            --------- `VoteCount` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/blockchain.rs:81:45
[INFO] [stdout]    |
[INFO] [stdout] 81 | #[derive(Clone, Eq, PartialEq, Debug, Hash, Serialize)]
[INFO] [stdout]    |                                             ^--------
[INFO] [stdout]    |                                             |
[INFO] [stdout]    |                                             `Serialize` is not local
[INFO] [stdout]    |                                             move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_ProtoBlock`
[INFO] [stdout] 82 | struct ProtoBlock<D: BlockData> {
[INFO] [stdout]    |        ---------- `ProtoBlock` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/justification.rs:82:17
[INFO] [stdout]    |
[INFO] [stdout] 82 |     pub fn iter(&self) -> std::slice::Iter<Message<E>> {
[INFO] [stdout]    |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                 |
[INFO] [stdout]    |                 the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 82 |     pub fn iter(&self) -> std::slice::Iter<'_, Message<E>> {
[INFO] [stdout]    |                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/justification.rs:86:21
[INFO] [stdout]    |
[INFO] [stdout] 86 |     pub fn par_iter(&self) -> rayon::slice::Iter<Message<E>> {
[INFO] [stdout]    |                     ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 86 |     pub fn par_iter(&self) -> rayon::slice::Iter<'_, Message<E>> {
[INFO] [stdout]    |                                                  +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/justification.rs:321:17
[INFO] [stdout]     |
[INFO] [stdout] 321 |     pub fn iter(&self) -> std::collections::hash_map::Iter<E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                 |
[INFO] [stdout]     |                 the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 321 |     pub fn iter(&self) -> std::collections::hash_map::Iter<'_, E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/justification.rs:335:17
[INFO] [stdout]     |
[INFO] [stdout] 335 |     pub fn keys(&self) -> std::collections::hash_map::Keys<E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                 |
[INFO] [stdout]     |                 the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 335 |     pub fn keys(&self) -> std::collections::hash_map::Keys<'_, E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/justification.rs:341:9
[INFO] [stdout]     |
[INFO] [stdout] 341 |         &self,
[INFO] [stdout]     |         ^^^^^ the lifetime is elided here
[INFO] [stdout] 342 |     ) -> std::collections::hash_map::Values<E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 342 |     ) -> std::collections::hash_map::Values<'_, E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/justification.rs:516:17
[INFO] [stdout]     |
[INFO] [stdout] 516 |     pub fn iter(&self) -> std::collections::hash_set::Iter<Message<E>> {
[INFO] [stdout]     |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                 |
[INFO] [stdout]     |                 the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 516 |     pub fn iter(&self) -> std::collections::hash_set::Iter<'_, Message<E>> {
[INFO] [stdout]     |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused return value of `finish` that must be used
[INFO] [stdout]   --> src/util/hash.rs:21:1
[INFO] [stdout]    |
[INFO] [stdout] 21 | / fixed_hash::construct_fixed_hash!(
[INFO] [stdout] 22 | |     pub struct Hash(64);
[INFO] [stdout] 23 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_must_use)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]    |
[INFO] [stdout] 21 | let _ = fixed_hash::construct_fixed_hash!(
[INFO] [stdout]    | +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:317:13
[INFO] [stdout]     |
[INFO] [stdout] 317 |     fn read(&self) -> LockResult<RwLockReadGuard<HashMap<V, U>>> {
[INFO] [stdout]     |             ^^^^^                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 317 |     fn read(&self) -> LockResult<RwLockReadGuard<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                  +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:322:14
[INFO] [stdout]     |
[INFO] [stdout] 322 |     fn write(&self) -> LockResult<RwLockWriteGuard<HashMap<V, U>>> {
[INFO] [stdout]     |              ^^^^^                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |              |
[INFO] [stdout]     |              the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 322 |     fn write(&self) -> LockResult<RwLockWriteGuard<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                    +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:327:19
[INFO] [stdout]     |
[INFO] [stdout] 327 |     pub fn insert(&mut self, validator: V, weight: U) -> Result<bool, Error<HashMap<V, U>>> {
[INFO] [stdout]     |                   ^^^^^^^^^ the lifetime is elided here               ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 327 |     pub fn insert(&mut self, validator: V, weight: U) -> Result<bool, Error<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:338:23
[INFO] [stdout]     |
[INFO] [stdout] 338 |     pub fn validators(&self) -> Result<HashSet<V>, Error<HashMap<V, U>>> {
[INFO] [stdout]     |                       ^^^^^                        ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                       |
[INFO] [stdout]     |                       the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 338 |     pub fn validators(&self) -> Result<HashSet<V>, Error<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                          +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:355:19
[INFO] [stdout]     |
[INFO] [stdout] 355 |     pub fn weight(&self, validator: &V) -> Result<U, Error<HashMap<V, U>>> {
[INFO] [stdout]     |                   ^^^^^ the lifetime is elided here  ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 355 |     pub fn weight(&self, validator: &V) -> Result<U, Error<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> examples/serde.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, PartialEq, Debug)]
[INFO] [stdout]    |          ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> examples/serde.rs:33:21
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, PartialEq, Debug)]
[INFO] [stdout]    |                     ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> examples/ternary.rs:35:68
[INFO] [stdout]    |
[INFO] [stdout] 35 | #[derive(Debug, Hash, Clone, Copy, Ord, PartialOrd, Eq, PartialEq, serde_derive::Serialize)]
[INFO] [stdout]    |                                                                    ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> benches/block.rs:35:68
[INFO] [stdout]    |
[INFO] [stdout] 35 | #[derive(Debug, Hash, Clone, Copy, Ord, PartialOrd, Eq, PartialEq, serde_derive::Serialize)]
[INFO] [stdout]    |                                                                    ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> examples/serde.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, PartialEq, Debug)]
[INFO] [stdout]    |          ^--------
[INFO] [stdout]    |          |
[INFO] [stdout]    |          `Serialize` is not local
[INFO] [stdout]    |          move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Example`
[INFO] [stdout] 34 | struct Example {
[INFO] [stdout]    |        ------- `Example` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> examples/serde.rs:33:21
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(Serialize, Deserialize, PartialEq, Debug)]
[INFO] [stdout]    |                     ^----------
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     `Deserialize` is not local
[INFO] [stdout]    |                     move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Example`
[INFO] [stdout] 34 | struct Example {
[INFO] [stdout]    |        ------- `Example` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Deserialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> tests/common/binary.rs:28:45
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[derive(Clone, Eq, PartialEq, Debug, Hash, serde_derive::Serialize)]
[INFO] [stdout]    |                                             ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/tests_common/integer.rs:32:62
[INFO] [stdout]    |
[INFO] [stdout] 32 | #[derive(Clone, Eq, Debug, Ord, PartialOrd, PartialEq, Hash, serde_derive::Serialize)]
[INFO] [stdout]    |                                                              ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/tests_common/vote_count.rs:50:70
[INFO] [stdout]    |
[INFO] [stdout] 50 | #[derive(Clone, Copy, Eq, Ord, PartialOrd, PartialEq, Hash, Default, serde_derive::Serialize)]
[INFO] [stdout]    |                                                                      ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy`
[INFO] [stdout]   --> src/blockchain.rs:81:45
[INFO] [stdout]    |
[INFO] [stdout] 81 | #[derive(Clone, Eq, PartialEq, Debug, Hash, Serialize)]
[INFO] [stdout]    |                                             ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `dev`
[INFO] [stdout]   --> src/util/hash.rs:21:1
[INFO] [stdout]    |
[INFO] [stdout] 21 | / fixed_hash::construct_fixed_hash!(
[INFO] [stdout] 22 | |     pub struct Hash(64);
[INFO] [stdout] 23 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fixed_hash::construct_fixed_hash` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fixed_hash::construct_fixed_hash` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> benches/block.rs:35:68
[INFO] [stdout]    |
[INFO] [stdout] 35 | #[derive(Debug, Hash, Clone, Copy, Ord, PartialOrd, Eq, PartialEq, serde_derive::Serialize)]
[INFO] [stdout]    |                                                                    ^----------------------
[INFO] [stdout]    |                                                                    |
[INFO] [stdout]    |                                                                    `Serialize` is not local
[INFO] [stdout]    |                                                                    move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Value`
[INFO] [stdout] 36 | pub enum Value {
[INFO] [stdout]    |          ----- `Value` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> tests/common/binary.rs:28:45
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[derive(Clone, Eq, PartialEq, Debug, Hash, serde_derive::Serialize)]
[INFO] [stdout]    |                                             ^----------------------
[INFO] [stdout]    |                                             |
[INFO] [stdout]    |                                             `Serialize` is not local
[INFO] [stdout]    |                                             move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_BoolWrapper`
[INFO] [stdout] 29 | pub struct BoolWrapper(pub bool);
[INFO] [stdout]    |            ----------- `BoolWrapper` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> examples/ternary.rs:35:68
[INFO] [stdout]    |
[INFO] [stdout] 35 | #[derive(Debug, Hash, Clone, Copy, Ord, PartialOrd, Eq, PartialEq, serde_derive::Serialize)]
[INFO] [stdout]    |                                                                    ^----------------------
[INFO] [stdout]    |                                                                    |
[INFO] [stdout]    |                                                                    `Serialize` is not local
[INFO] [stdout]    |                                                                    move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Value`
[INFO] [stdout] 36 | pub enum Value {
[INFO] [stdout]    |          ----- `Value` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: struct `Tx` is never constructed
[INFO] [stdout]   --> src/tests_common/integer.rs:49:12
[INFO] [stdout]    |
[INFO] [stdout] 49 | pub struct Tx;
[INFO] [stdout]    |            ^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/tests_common/integer.rs:32:62
[INFO] [stdout]    |
[INFO] [stdout] 32 | #[derive(Clone, Eq, Debug, Ord, PartialOrd, PartialEq, Hash, serde_derive::Serialize)]
[INFO] [stdout]    |                                                              ^----------------------
[INFO] [stdout]    |                                                              |
[INFO] [stdout]    |                                                              `Serialize` is not local
[INFO] [stdout]    |                                                              move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_IntegerWrapper`
[INFO] [stdout] 33 | pub struct IntegerWrapper(pub u32);
[INFO] [stdout]    |            -------------- `IntegerWrapper` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/tests_common/vote_count.rs:50:70
[INFO] [stdout]    |
[INFO] [stdout] 50 | #[derive(Clone, Copy, Eq, Ord, PartialOrd, PartialEq, Hash, Default, serde_derive::Serialize)]
[INFO] [stdout]    |                                                                      ^----------------------
[INFO] [stdout]    |                                                                      |
[INFO] [stdout]    |                                                                      `Serialize` is not local
[INFO] [stdout]    |                                                                      move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_VoteCount`
[INFO] [stdout] 51 | pub struct VoteCount {
[INFO] [stdout]    |            --------- `VoteCount` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `serde_derive::Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/blockchain.rs:81:45
[INFO] [stdout]    |
[INFO] [stdout] 81 | #[derive(Clone, Eq, PartialEq, Debug, Hash, Serialize)]
[INFO] [stdout]    |                                             ^--------
[INFO] [stdout]    |                                             |
[INFO] [stdout]    |                                             `Serialize` is not local
[INFO] [stdout]    |                                             move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_ProtoBlock`
[INFO] [stdout] 82 | struct ProtoBlock<D: BlockData> {
[INFO] [stdout]    |        ---------- `ProtoBlock` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the derive macro `Serialize` may come from an old version of the `serde_derive` crate, try updating your dependency with `cargo update -p serde_derive`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/blockchain.rs:922:9
[INFO] [stdout]     |
[INFO] [stdout] 922 | /         float_eq!(
[INFO] [stdout] 923 | |             genesis.score(
[INFO] [stdout] 924 | |                 &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()),
[INFO] [stdout] 925 | |                 &weights
[INFO] [stdout] 926 | |             ),
[INFO] [stdout] 927 | |             31.0
[INFO] [stdout] 928 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: `#[warn(non_fmt_panics)]` (part of `#[warn(rust_2021_compatibility)]`) on by default
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/blockchain.rs:929:9
[INFO] [stdout]     |
[INFO] [stdout] 929 | /         float_eq!(
[INFO] [stdout] 930 | |             block_1.score(
[INFO] [stdout] 931 | |                 &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()),
[INFO] [stdout] 932 | |                 &weights
[INFO] [stdout] 933 | |             ),
[INFO] [stdout] 934 | |             31.0
[INFO] [stdout] 935 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/blockchain.rs:936:9
[INFO] [stdout]     |
[INFO] [stdout] 936 | /         float_eq!(
[INFO] [stdout] 937 | |             block_2.score(
[INFO] [stdout] 938 | |                 &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()),
[INFO] [stdout] 939 | |                 &weights
[INFO] [stdout] 940 | |             ),
[INFO] [stdout] 941 | |             4.0
[INFO] [stdout] 942 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/blockchain.rs:943:9
[INFO] [stdout]     |
[INFO] [stdout] 943 | /         float_eq!(
[INFO] [stdout] 944 | |             block_3.score(
[INFO] [stdout] 945 | |                 &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()),
[INFO] [stdout] 946 | |                 &weights
[INFO] [stdout] 947 | |             ),
[INFO] [stdout] 948 | |             25.0
[INFO] [stdout] 949 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/blockchain.rs:950:9
[INFO] [stdout]     |
[INFO] [stdout] 950 | /         float_eq!(
[INFO] [stdout] 951 | |             block_4.score(
[INFO] [stdout] 952 | |                 &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()),
[INFO] [stdout] 953 | |                 &weights
[INFO] [stdout] 954 | |             ),
[INFO] [stdout] 955 | |             17.0
[INFO] [stdout] 956 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/blockchain.rs:957:9
[INFO] [stdout]     |
[INFO] [stdout] 957 | /         float_eq!(
[INFO] [stdout] 958 | |             block_5.score(
[INFO] [stdout] 959 | |                 &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()),
[INFO] [stdout] 960 | |                 &weights
[INFO] [stdout] 961 | |             ),
[INFO] [stdout] 962 | |             16.0
[INFO] [stdout] 963 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/justification.rs:82:17
[INFO] [stdout]    |
[INFO] [stdout] 82 |     pub fn iter(&self) -> std::slice::Iter<Message<E>> {
[INFO] [stdout]    |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                 |
[INFO] [stdout]    |                 the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 82 |     pub fn iter(&self) -> std::slice::Iter<'_, Message<E>> {
[INFO] [stdout]    |                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/justification.rs:86:21
[INFO] [stdout]    |
[INFO] [stdout] 86 |     pub fn par_iter(&self) -> rayon::slice::Iter<Message<E>> {
[INFO] [stdout]    |                     ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                     |
[INFO] [stdout]    |                     the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 86 |     pub fn par_iter(&self) -> rayon::slice::Iter<'_, Message<E>> {
[INFO] [stdout]    |                                                  +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/justification.rs:321:17
[INFO] [stdout]     |
[INFO] [stdout] 321 |     pub fn iter(&self) -> std::collections::hash_map::Iter<E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                 |
[INFO] [stdout]     |                 the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 321 |     pub fn iter(&self) -> std::collections::hash_map::Iter<'_, E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/justification.rs:335:17
[INFO] [stdout]     |
[INFO] [stdout] 335 |     pub fn keys(&self) -> std::collections::hash_map::Keys<E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                 |
[INFO] [stdout]     |                 the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 335 |     pub fn keys(&self) -> std::collections::hash_map::Keys<'_, E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/justification.rs:341:9
[INFO] [stdout]     |
[INFO] [stdout] 341 |         &self,
[INFO] [stdout]     |         ^^^^^ the lifetime is elided here
[INFO] [stdout] 342 |     ) -> std::collections::hash_map::Values<E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 342 |     ) -> std::collections::hash_map::Values<'_, E::ValidatorName, HashSet<Message<E>>> {
[INFO] [stdout]     |                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/justification.rs:516:17
[INFO] [stdout]     |
[INFO] [stdout] 516 |     pub fn iter(&self) -> std::collections::hash_set::Iter<Message<E>> {
[INFO] [stdout]     |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                 |
[INFO] [stdout]     |                 the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 516 |     pub fn iter(&self) -> std::collections::hash_set::Iter<'_, Message<E>> {
[INFO] [stdout]     |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:580:9
[INFO] [stdout]     |
[INFO] [stdout] 580 |         float_eq!(validator_state.fault_weight(), 3.0);
[INFO] [stdout]     |         ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:626:9
[INFO] [stdout]     |
[INFO] [stdout] 626 |         float_eq!(validator_state.fault_weight(), 3.0);
[INFO] [stdout]     |         ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:32:13
[INFO] [stdout]     |
[INFO] [stdout]  32 | /             format!(
[INFO] [stdout]  33 | |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 | |                 $lhs, $rhs, $message
[INFO] [stdout]  35 | |             ),
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:691:9
[INFO] [stdout]     |
[INFO] [stdout] 691 | /         float_eq!(
[INFO] [stdout] 692 | |             state.fault_weight(),
[INFO] [stdout] 693 | |             1.0,
[INFO] [stdout] 694 | |             "$v0_prime$ conflicts with $v0$ through $m0$, but we should accept this fault as it \
[INFO] [stdout] 695 | |              doesnt cross the fault threshold for the set, and thus the state_fault_weight should \
[INFO] [stdout] 696 | |              be incremented to 1.0"
[INFO] [stdout] 697 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  32 ~             
[INFO] [stdout]  33 |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 |                 $lhs, $rhs, $message
[INFO] [stdout]  35 ~             ,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:32:13
[INFO] [stdout]     |
[INFO] [stdout]  32 | /             format!(
[INFO] [stdout]  33 | |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 | |                 $lhs, $rhs, $message
[INFO] [stdout]  35 | |             ),
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:731:9
[INFO] [stdout]     |
[INFO] [stdout] 731 | /         float_eq!(
[INFO] [stdout] 732 | |             state.fault_weight(),
[INFO] [stdout] 733 | |             0.1,
[INFO] [stdout] 734 | |             "$v0_prime$ conflicts with $v0$ through $m0$, and we should NOT accept this fault as \
[INFO] [stdout] 735 | |              the fault threshold gets crossed for the set, and thus the state_fault_weight should \
[INFO] [stdout] 736 | |              not be incremented"
[INFO] [stdout] 737 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  32 ~             
[INFO] [stdout]  33 |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 |                 $lhs, $rhs, $message
[INFO] [stdout]  35 ~             ,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:32:13
[INFO] [stdout]     |
[INFO] [stdout]  32 | /             format!(
[INFO] [stdout]  33 | |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 | |                 $lhs, $rhs, $message
[INFO] [stdout]  35 | |             ),
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:768:9
[INFO] [stdout]     |
[INFO] [stdout] 768 | /         float_eq!(
[INFO] [stdout] 769 | |             state.fault_weight(),
[INFO] [stdout] 770 | |             2.0,
[INFO] [stdout] 771 | |             "$v0_prime$ conflict with $v0$ through $m0$, but we should NOT accept this fault as \
[INFO] [stdout] 772 | |              we can't know the weight of the validator, which could be Infinity, and thus the \
[INFO] [stdout] 773 | |              state_fault_weight should be unchanged"
[INFO] [stdout] 774 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  32 ~             
[INFO] [stdout]  33 |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 |                 $lhs, $rhs, $message
[INFO] [stdout]  35 ~             ,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:32:13
[INFO] [stdout]     |
[INFO] [stdout]  32 | /             format!(
[INFO] [stdout]  33 | |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 | |                 $lhs, $rhs, $message
[INFO] [stdout]  35 | |             ),
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:809:9
[INFO] [stdout]     |
[INFO] [stdout] 809 | /         float_eq!(
[INFO] [stdout] 810 | |             state.fault_weight(),
[INFO] [stdout] 811 | |             1.0,
[INFO] [stdout] 812 | |             "$v0_prime$ conflict with $v0$ through $m0$, but we should NOT accept this fault as \
[INFO] [stdout] 813 | |              we can't know the weight of the validator, which could be Infinity, and thus the \
[INFO] [stdout] 814 | |              state_fault_weight should be unchanged"
[INFO] [stdout] 815 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  32 ~             
[INFO] [stdout]  33 |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 |                 $lhs, $rhs, $message
[INFO] [stdout]  35 ~             ,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:845:9
[INFO] [stdout]     |
[INFO] [stdout] 845 |         float_eq!(validator_state.fault_weight(), 1.0);
[INFO] [stdout]     |         ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:877:9
[INFO] [stdout]     |
[INFO] [stdout] 877 | /         float_eq!(
[INFO] [stdout] 878 | |             validator_state.validators_weights().weight(&0).unwrap(),
[INFO] [stdout] 879 | |             0.0
[INFO] [stdout] 880 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/justification.rs:881:9
[INFO] [stdout]     |
[INFO] [stdout] 881 |         float_eq!(validator_state.fault_weight(), 0.0);
[INFO] [stdout]     |         ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused return value of `finish` that must be used
[INFO] [stdout]   --> src/util/hash.rs:21:1
[INFO] [stdout]    |
[INFO] [stdout] 21 | / fixed_hash::construct_fixed_hash!(
[INFO] [stdout] 22 | |     pub struct Hash(64);
[INFO] [stdout] 23 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_must_use)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]    |
[INFO] [stdout] 21 | let _ = fixed_hash::construct_fixed_hash!(
[INFO] [stdout]    | +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:317:13
[INFO] [stdout]     |
[INFO] [stdout] 317 |     fn read(&self) -> LockResult<RwLockReadGuard<HashMap<V, U>>> {
[INFO] [stdout]     |             ^^^^^                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |             |
[INFO] [stdout]     |             the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 317 |     fn read(&self) -> LockResult<RwLockReadGuard<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                  +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:322:14
[INFO] [stdout]     |
[INFO] [stdout] 322 |     fn write(&self) -> LockResult<RwLockWriteGuard<HashMap<V, U>>> {
[INFO] [stdout]     |              ^^^^^                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |              |
[INFO] [stdout]     |              the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 322 |     fn write(&self) -> LockResult<RwLockWriteGuard<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                    +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:327:19
[INFO] [stdout]     |
[INFO] [stdout] 327 |     pub fn insert(&mut self, validator: V, weight: U) -> Result<bool, Error<HashMap<V, U>>> {
[INFO] [stdout]     |                   ^^^^^^^^^ the lifetime is elided here               ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 327 |     pub fn insert(&mut self, validator: V, weight: U) -> Result<bool, Error<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                                             +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:338:23
[INFO] [stdout]     |
[INFO] [stdout] 338 |     pub fn validators(&self) -> Result<HashSet<V>, Error<HashMap<V, U>>> {
[INFO] [stdout]     |                       ^^^^^                        ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                       |
[INFO] [stdout]     |                       the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 338 |     pub fn validators(&self) -> Result<HashSet<V>, Error<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                          +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/validator.rs:355:19
[INFO] [stdout]     |
[INFO] [stdout] 355 |     pub fn weight(&self, validator: &V) -> Result<U, Error<HashMap<V, U>>> {
[INFO] [stdout]     |                   ^^^^^ the lifetime is elided here  ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 355 |     pub fn weight(&self, validator: &V) -> Result<U, Error<'_, HashMap<V, U>>> {
[INFO] [stdout]     |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/validator.rs:459:9
[INFO] [stdout]     |
[INFO] [stdout] 459 |         float_eq!(weights.weight(&0).unwrap(), 1.0);
[INFO] [stdout]     |         ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/validator.rs:460:9
[INFO] [stdout]     |
[INFO] [stdout] 460 |         float_eq!(weights.weight(&1).unwrap(), -1.0);
[INFO] [stdout]     |         -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/validator.rs:483:9
[INFO] [stdout]     |
[INFO] [stdout] 483 | /         float_eq!(
[INFO] [stdout] 484 | |             weights.sum_weight_validators(&HashSet::from_iter(vec![0, 1])),
[INFO] [stdout] 485 | |             0.0
[INFO] [stdout] 486 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/validator.rs:487:9
[INFO] [stdout]     |
[INFO] [stdout] 487 | /         float_eq!(
[INFO] [stdout] 488 | |             weights.sum_weight_validators(&HashSet::from_iter(vec![0, 2])),
[INFO] [stdout] 489 | |             4.3
[INFO] [stdout] 490 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:26:13
[INFO] [stdout]     |
[INFO] [stdout]  26 |               format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/validator.rs:500:9
[INFO] [stdout]     |
[INFO] [stdout] 500 | /         float_eq!(
[INFO] [stdout] 501 | |             weights.sum_all_weights(),
[INFO] [stdout] 502 | |             weights.sum_weight_validators(&HashSet::from_iter(vec![0, 2]))
[INFO] [stdout] 503 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  26 -             format!("float_eq: {} and {} aren't equal", $lhs, $rhs),
[INFO] [stdout]  26 +             "float_eq: {} and {} aren't equal", $lhs, $rhs,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:32:13
[INFO] [stdout]     |
[INFO] [stdout]  32 | /             format!(
[INFO] [stdout]  33 | |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 | |                 $lhs, $rhs, $message
[INFO] [stdout]  35 | |             ),
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/validator.rs:543:9
[INFO] [stdout]     |
[INFO] [stdout] 543 | /         float_eq!(
[INFO] [stdout] 544 | |             validator_state.fault_weight(),
[INFO] [stdout] 545 | |             0.0,
[INFO] [stdout] 546 | |             "fault weight should be 0"
[INFO] [stdout] 547 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  32 ~             
[INFO] [stdout]  33 |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 |                 $lhs, $rhs, $message
[INFO] [stdout]  35 ~             ,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:32:13
[INFO] [stdout]     |
[INFO] [stdout]  32 | /             format!(
[INFO] [stdout]  33 | |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 | |                 $lhs, $rhs, $message
[INFO] [stdout]  35 | |             ),
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/validator.rs:596:9
[INFO] [stdout]     |
[INFO] [stdout] 596 | /         float_eq!(
[INFO] [stdout] 597 | |             validator_state.fault_weight(),
[INFO] [stdout] 598 | |             1.0,
[INFO] [stdout] 599 | |             "fault weight should be 1"
[INFO] [stdout] 600 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  32 ~             
[INFO] [stdout]  33 |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 |                 $lhs, $rhs, $message
[INFO] [stdout]  35 ~             ,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/tests_common/utils.rs:32:13
[INFO] [stdout]     |
[INFO] [stdout]  32 | /             format!(
[INFO] [stdout]  33 | |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 | |                 $lhs, $rhs, $message
[INFO] [stdout]  35 | |             ),
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/validator.rs:649:9
[INFO] [stdout]     |
[INFO] [stdout] 649 | /         float_eq!(
[INFO] [stdout] 650 | |             validator_state.fault_weight(),
[INFO] [stdout] 651 | |             0.0,
[INFO] [stdout] 652 | |             "fault weight should be 0"
[INFO] [stdout] 653 | |         );
[INFO] [stdout]     | |_________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout]  32 ~             
[INFO] [stdout]  33 |                 "float_eq: {} and {} aren't equal. Provided message: {}",
[INFO] [stdout]  34 |                 $lhs, $rhs, $message
[INFO] [stdout]  35 ~             ,
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 12.03s
[INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: criterion v0.2.11
[INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 5`
[INFO] running `Command { std: "docker" "inspect" "c2d9fb05bf4f691f3e2af358a8676d0946d14dbcad423b3f34a585f248fb67bd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c2d9fb05bf4f691f3e2af358a8676d0946d14dbcad423b3f34a585f248fb67bd", kill_on_drop: false }`
[INFO] [stdout] c2d9fb05bf4f691f3e2af358a8676d0946d14dbcad423b3f34a585f248fb67bd
