[INFO] fetching crate core_cbc_casper 0.1.0... [INFO] testing core_cbc_casper-0.1.0 against master#cdb45c87e2cd43495379f7e867e3cc15dcee9f93 for pr-145838-1 [INFO] extracting crate core_cbc_casper 0.1.0 into /workspace/builds/worker-4-tc1/source [INFO] removed /workspace/builds/worker-4-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-4-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate core_cbc_casper 0.1.0 on toolchain cdb45c87e2cd43495379f7e867e3cc15dcee9f93 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "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" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded static_assertions v0.2.5 [INFO] [stderr] Downloaded fixed-hash v0.3.2 [INFO] [stderr] Downloaded rand_xoshiro v0.1.0 [INFO] [stderr] Downloaded criterion-plot v0.3.1 [INFO] [stderr] Downloaded criterion v0.2.11 [INFO] [stderr] Downloaded tinytemplate v1.0.2 [INFO] [stderr] Downloaded rusty-fork v0.2.2 [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-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 19aefe29080fcd7e2eb3ba6f6688e6451b352a192c8b6655c34a796ddf1e4a01 [INFO] running `Command { std: "docker" "start" "-a" "19aefe29080fcd7e2eb3ba6f6688e6451b352a192c8b6655c34a796ddf1e4a01", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "19aefe29080fcd7e2eb3ba6f6688e6451b352a192c8b6655c34a796ddf1e4a01", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "19aefe29080fcd7e2eb3ba6f6688e6451b352a192c8b6655c34a796ddf1e4a01", kill_on_drop: false }` [INFO] [stdout] 19aefe29080fcd7e2eb3ba6f6688e6451b352a192c8b6655c34a796ddf1e4a01 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] c29836792d3c2fe19fd1987277354a8765b4425da7a4583fb969c32c4ce48239 [INFO] running `Command { std: "docker" "start" "-a" "c29836792d3c2fe19fd1987277354a8765b4425da7a4583fb969c32c4ce48239", kill_on_drop: false }` [INFO] [stderr] Compiling autocfg v0.1.7 [INFO] [stderr] Compiling libc v0.2.65 [INFO] [stderr] Compiling typenum v1.11.2 [INFO] [stderr] Compiling proc-macro2 v1.0.6 [INFO] [stderr] Compiling scopeguard v1.0.0 [INFO] [stderr] Compiling byteorder v1.3.2 [INFO] [stderr] Compiling serde v1.0.102 [INFO] [stderr] Compiling syn v1.0.8 [INFO] [stderr] Compiling rayon-core v1.7.0 [INFO] [stderr] Compiling either v1.5.3 [INFO] [stderr] Compiling constant_time_eq v0.1.4 [INFO] [stderr] Compiling byte-tools v0.2.0 [INFO] [stderr] Compiling static_assertions v0.2.5 [INFO] [stderr] Compiling memoffset v0.5.3 [INFO] [stderr] Compiling itertools v0.7.11 [INFO] [stderr] Compiling crossbeam-utils v0.7.0 [INFO] [stderr] Compiling crossbeam-epoch v0.8.0 [INFO] [stderr] Compiling bincode v1.2.0 [INFO] [stderr] Compiling crossbeam-queue v0.2.0 [INFO] [stderr] Compiling quote v1.0.2 [INFO] [stderr] Compiling num_cpus v1.11.1 [INFO] [stderr] Compiling fixed-hash v0.3.2 [INFO] [stderr] Compiling generic-array v0.9.0 [INFO] [stderr] Compiling crossbeam-deque v0.7.2 [INFO] [stderr] Compiling digest v0.7.6 [INFO] [stderr] Compiling crypto-mac v0.5.2 [INFO] [stderr] Compiling blake2 v0.7.1 [INFO] [stderr] Compiling rayon v1.3.0 [INFO] [stderr] Compiling serde_derive v1.0.102 [INFO] [stderr] Compiling 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] = help: 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: see 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] = help: 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: see 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] = help: 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: see 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] = help: the macro `fixed_hash::construct_fixed_hash` may come from an old version of the `fixed_hash` crate, try updating your dependency with `cargo update -p fixed_hash` [INFO] [stdout] = note: see 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 { [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> { [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> { [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> { [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> { [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>> { [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>> { [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>> { [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>> { [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>> { [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>> { [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> { [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> { [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>> { [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>> { [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>> { [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>> { [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>> { [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>> { [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, Error>> { [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, Error<'_, HashMap>> { [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>> { [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>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 10.03s [INFO] running `Command { std: "docker" "inspect" "c29836792d3c2fe19fd1987277354a8765b4425da7a4583fb969c32c4ce48239", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c29836792d3c2fe19fd1987277354a8765b4425da7a4583fb969c32c4ce48239", kill_on_drop: false }` [INFO] [stdout] c29836792d3c2fe19fd1987277354a8765b4425da7a4583fb969c32c4ce48239 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 9d3bcad6aea0e1286c15753d98f38eb5595e53917cf61099e63dee99a110698e [INFO] running `Command { std: "docker" "start" "-a" "9d3bcad6aea0e1286c15753d98f38eb5595e53917cf61099e63dee99a110698e", kill_on_drop: false }` [INFO] [stderr] Compiling memchr v2.2.1 [INFO] [stderr] Compiling itoa v0.4.4 [INFO] [stderr] Compiling num-traits v0.2.9 [INFO] [stderr] Compiling cast v0.2.3 [INFO] [stderr] Compiling regex-automata v0.1.8 [INFO] [stderr] Compiling unicode-width v0.1.6 [INFO] [stderr] Compiling itertools v0.8.1 [INFO] [stderr] Compiling same-file v1.0.5 [INFO] [stderr] Compiling rand_xoshiro v0.1.0 [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] = help: 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: see 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] [stderr] Compiling atty v0.2.13 [INFO] [stderr] Compiling rand_os v0.1.3 [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] = help: 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: see 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] = help: 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: see 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] = help: the macro `fixed_hash::construct_fixed_hash` may come from an old version of the `fixed_hash` crate, try updating your dependency with `cargo update -p fixed_hash` [INFO] [stdout] = note: see 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 { [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> { [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> { [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> { [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> { [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>> { [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>> { [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>> { [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>> { [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>> { [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>> { [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> { [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> { [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>> { [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>> { [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>> { [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>> { [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>> { [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>> { [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, Error>> { [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, Error<'_, HashMap>> { [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>> { [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>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling serde_json v1.0.41 [INFO] [stderr] Compiling textwrap v0.11.0 [INFO] [stderr] Compiling walkdir v2.2.9 [INFO] [stderr] Compiling clap v2.33.0 [INFO] [stderr] Compiling bstr v0.2.8 [INFO] [stderr] Compiling csv-core v0.1.6 [INFO] [stderr] Compiling tinytemplate v1.0.2 [INFO] [stderr] Compiling criterion-plot v0.3.1 [INFO] [stderr] Compiling csv v1.1.1 [INFO] [stderr] Compiling criterion v0.2.11 [INFO] [stderr] Compiling core_cbc_casper v0.1.0 (/opt/rustwide/workdir) [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] = help: 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: see 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] = help: 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: see 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] --> 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] = help: 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: see 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] --> 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] = help: 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: see 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] = help: 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: see 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] = help: 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: see 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] = help: 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: see 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] = help: the macro `fixed_hash::construct_fixed_hash` may come from an old version of the `fixed_hash` crate, try updating your dependency with `cargo update -p fixed_hash` [INFO] [stdout] = note: see 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] --> 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: 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: 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: 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 { [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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> { [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> { [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> { [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> { [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>> { [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>> { [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>> { [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>> { [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>> { [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>> { [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> { [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> { [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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>> { [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>> { [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>> { [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>> { [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>> { [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>> { [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, Error>> { [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, Error<'_, HashMap>> { [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>> { [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>> { [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 [INFO] [stdout] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [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 `test` profile [unoptimized + debuginfo] target(s) in 12.51s [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 1` [INFO] running `Command { std: "docker" "inspect" "9d3bcad6aea0e1286c15753d98f38eb5595e53917cf61099e63dee99a110698e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "9d3bcad6aea0e1286c15753d98f38eb5595e53917cf61099e63dee99a110698e", kill_on_drop: false }` [INFO] [stdout] 9d3bcad6aea0e1286c15753d98f38eb5595e53917cf61099e63dee99a110698e [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] 13ecb1e5dcff7cbdc8c6acb31ccc059a2b4e52df2940b4c9748ce084e345b4e4 [INFO] running `Command { std: "docker" "start" "-a" "13ecb1e5dcff7cbdc8c6acb31ccc059a2b4e52df2940b4c9748ce084e345b4e4", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/tests_common/integer.rs:32:62 [INFO] [stderr] | [INFO] [stderr] 32 | #[derive(Clone, Eq, Debug, Ord, PartialOrd, PartialEq, Hash, serde_derive::Serialize)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand` [INFO] [stderr] = 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] [stderr] = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/tests_common/vote_count.rs:50:70 [INFO] [stderr] | [INFO] [stderr] 50 | #[derive(Clone, Copy, Eq, Ord, PartialOrd, PartialEq, Hash, Default, serde_derive::Serialize)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand` [INFO] [stderr] = 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] [stderr] = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/blockchain.rs:81:45 [INFO] [stderr] | [INFO] [stderr] 81 | #[derive(Clone, Eq, PartialEq, Debug, Hash, Serialize)] [INFO] [stderr] | ^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand` [INFO] [stderr] = 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] [stderr] = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `dev` [INFO] [stderr] --> src/util/hash.rs:21:1 [INFO] [stderr] | [INFO] [stderr] 21 | / fixed_hash::construct_fixed_hash!( [INFO] [stderr] 22 | | pub struct Hash(64); [INFO] [stderr] 23 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `fixed_hash::construct_fixed_hash` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `fixed_hash::construct_fixed_hash` may come from an old version of the `fixed_hash` crate, try updating your dependency with `cargo update -p fixed_hash` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `fixed_hash::construct_fixed_hash` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: struct `Tx` is never constructed [INFO] [stderr] --> src/tests_common/integer.rs:49:12 [INFO] [stderr] | [INFO] [stderr] 49 | pub struct Tx; [INFO] [stderr] | ^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> src/tests_common/integer.rs:32:62 [INFO] [stderr] | [INFO] [stderr] 32 | #[derive(Clone, Eq, Debug, Ord, PartialOrd, PartialEq, Hash, serde_derive::Serialize)] [INFO] [stderr] | ^---------------------- [INFO] [stderr] | | [INFO] [stderr] | `Serialize` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_IntegerWrapper` [INFO] [stderr] 33 | pub struct IntegerWrapper(pub u32); [INFO] [stderr] | -------------- `IntegerWrapper` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = 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] [stderr] = 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] [stderr] = 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] [stderr] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> src/tests_common/vote_count.rs:50:70 [INFO] [stderr] | [INFO] [stderr] 50 | #[derive(Clone, Copy, Eq, Ord, PartialOrd, PartialEq, Hash, Default, serde_derive::Serialize)] [INFO] [stderr] | ^---------------------- [INFO] [stderr] | | [INFO] [stderr] | `Serialize` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_VoteCount` [INFO] [stderr] 51 | pub struct VoteCount { [INFO] [stderr] | --------- `VoteCount` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = 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] [stderr] = 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] [stderr] = 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] [stderr] = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> src/blockchain.rs:81:45 [INFO] [stderr] | [INFO] [stderr] 81 | #[derive(Clone, Eq, PartialEq, Debug, Hash, Serialize)] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Serialize` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_ProtoBlock` [INFO] [stderr] 82 | struct ProtoBlock { [INFO] [stderr] | ---------- `ProtoBlock` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = 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] [stderr] = 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] [stderr] = 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] [stderr] = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/justification.rs:82:17 [INFO] [stderr] | [INFO] [stderr] 82 | pub fn iter(&self) -> std::slice::Iter> { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 82 | pub fn iter(&self) -> std::slice::Iter<'_, Message> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/justification.rs:86:21 [INFO] [stderr] | [INFO] [stderr] 86 | pub fn par_iter(&self) -> rayon::slice::Iter> { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 86 | pub fn par_iter(&self) -> rayon::slice::Iter<'_, Message> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/justification.rs:321:17 [INFO] [stderr] | [INFO] [stderr] 321 | pub fn iter(&self) -> std::collections::hash_map::Iter>> { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 321 | pub fn iter(&self) -> std::collections::hash_map::Iter<'_, E::ValidatorName, HashSet>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/justification.rs:335:17 [INFO] [stderr] | [INFO] [stderr] 335 | pub fn keys(&self) -> std::collections::hash_map::Keys>> { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 335 | pub fn keys(&self) -> std::collections::hash_map::Keys<'_, E::ValidatorName, HashSet>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/justification.rs:341:9 [INFO] [stderr] | [INFO] [stderr] 341 | &self, [INFO] [stderr] | ^^^^^ the lifetime is elided here [INFO] [stderr] 342 | ) -> std::collections::hash_map::Values>> { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 342 | ) -> std::collections::hash_map::Values<'_, E::ValidatorName, HashSet>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/justification.rs:516:17 [INFO] [stderr] | [INFO] [stderr] 516 | pub fn iter(&self) -> std::collections::hash_set::Iter> { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 516 | pub fn iter(&self) -> std::collections::hash_set::Iter<'_, Message> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: unused return value of `finish` that must be used [INFO] [stderr] --> src/util/hash.rs:21:1 [INFO] [stderr] | [INFO] [stderr] 21 | / fixed_hash::construct_fixed_hash!( [INFO] [stderr] 22 | | pub struct Hash(64); [INFO] [stderr] 23 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(unused_must_use)]` (part of `#[warn(unused)]`) on by default [INFO] [stderr] help: use `let _ = ...` to ignore the resulting value [INFO] [stderr] | [INFO] [stderr] 21 | let _ = fixed_hash::construct_fixed_hash!( [INFO] [stderr] | +++++++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/validator.rs:317:13 [INFO] [stderr] | [INFO] [stderr] 317 | fn read(&self) -> LockResult>> { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 317 | fn read(&self) -> LockResult>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/validator.rs:322:14 [INFO] [stderr] | [INFO] [stderr] 322 | fn write(&self) -> LockResult>> { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 322 | fn write(&self) -> LockResult>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/validator.rs:327:19 [INFO] [stderr] | [INFO] [stderr] 327 | pub fn insert(&mut self, validator: V, weight: U) -> Result>> { [INFO] [stderr] | ^^^^^^^^^ the lifetime is elided here ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 327 | pub fn insert(&mut self, validator: V, weight: U) -> Result>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/validator.rs:338:23 [INFO] [stderr] | [INFO] [stderr] 338 | pub fn validators(&self) -> Result, Error>> { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 338 | pub fn validators(&self) -> Result, Error<'_, HashMap>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/validator.rs:355:19 [INFO] [stderr] | [INFO] [stderr] 355 | pub fn weight(&self, validator: &V) -> Result>> { [INFO] [stderr] | ^^^^^ the lifetime is elided here ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 355 | pub fn weight(&self, validator: &V) -> Result>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: `core_cbc_casper` (lib) generated 20 warnings (run `cargo fix --lib -p core_cbc_casper` to apply 11 suggestions) [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> examples/ternary.rs:35:68 [INFO] [stderr] | [INFO] [stderr] 35 | #[derive(Debug, Hash, Clone, Copy, Ord, PartialOrd, Eq, PartialEq, serde_derive::Serialize)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand` [INFO] [stderr] = 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] [stderr] = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> examples/ternary.rs:35:68 [INFO] [stderr] | [INFO] [stderr] 35 | #[derive(Debug, Hash, Clone, Copy, Ord, PartialOrd, Eq, PartialEq, serde_derive::Serialize)] [INFO] [stderr] | ^---------------------- [INFO] [stderr] | | [INFO] [stderr] | `Serialize` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Value` [INFO] [stderr] 36 | pub enum Value { [INFO] [stderr] | ----- `Value` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = 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] [stderr] = 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] [stderr] = 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] [stderr] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/blockchain.rs:922:9 [INFO] [stderr] | [INFO] [stderr] 922 | / float_eq!( [INFO] [stderr] 923 | | genesis.score( [INFO] [stderr] 924 | | &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()), [INFO] [stderr] 925 | | &weights [INFO] [stderr] 926 | | ), [INFO] [stderr] 927 | | 31.0 [INFO] [stderr] 928 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: `#[warn(non_fmt_panics)]` (part of `#[warn(rust_2021_compatibility)]`) on by default [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/blockchain.rs:929:9 [INFO] [stderr] | [INFO] [stderr] 929 | / float_eq!( [INFO] [stderr] 930 | | block_1.score( [INFO] [stderr] 931 | | &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()), [INFO] [stderr] 932 | | &weights [INFO] [stderr] 933 | | ), [INFO] [stderr] 934 | | 31.0 [INFO] [stderr] 935 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/blockchain.rs:936:9 [INFO] [stderr] | [INFO] [stderr] 936 | / float_eq!( [INFO] [stderr] 937 | | block_2.score( [INFO] [stderr] 938 | | &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()), [INFO] [stderr] 939 | | &weights [INFO] [stderr] 940 | | ), [INFO] [stderr] 941 | | 4.0 [INFO] [stderr] 942 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/blockchain.rs:943:9 [INFO] [stderr] | [INFO] [stderr] 943 | / float_eq!( [INFO] [stderr] 944 | | block_3.score( [INFO] [stderr] 945 | | &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()), [INFO] [stderr] 946 | | &weights [INFO] [stderr] 947 | | ), [INFO] [stderr] 948 | | 25.0 [INFO] [stderr] 949 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/blockchain.rs:950:9 [INFO] [stderr] | [INFO] [stderr] 950 | / float_eq!( [INFO] [stderr] 951 | | block_4.score( [INFO] [stderr] 952 | | &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()), [INFO] [stderr] 953 | | &weights [INFO] [stderr] 954 | | ), [INFO] [stderr] 955 | | 17.0 [INFO] [stderr] 956 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/blockchain.rs:957:9 [INFO] [stderr] | [INFO] [stderr] 957 | / float_eq!( [INFO] [stderr] 958 | | block_5.score( [INFO] [stderr] 959 | | &LatestMessagesHonest::from_latest_messages(&latest_messages, &HashSet::new()), [INFO] [stderr] 960 | | &weights [INFO] [stderr] 961 | | ), [INFO] [stderr] 962 | | 16.0 [INFO] [stderr] 963 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:580:9 [INFO] [stderr] | [INFO] [stderr] 580 | float_eq!(validator_state.fault_weight(), 3.0); [INFO] [stderr] | ---------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:626:9 [INFO] [stderr] | [INFO] [stderr] 626 | float_eq!(validator_state.fault_weight(), 3.0); [INFO] [stderr] | ---------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:32:13 [INFO] [stderr] | [INFO] [stderr] 32 | / format!( [INFO] [stderr] 33 | | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | | $lhs, $rhs, $message [INFO] [stderr] 35 | | ), [INFO] [stderr] | |_____________^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:691:9 [INFO] [stderr] | [INFO] [stderr] 691 | / float_eq!( [INFO] [stderr] 692 | | state.fault_weight(), [INFO] [stderr] 693 | | 1.0, [INFO] [stderr] 694 | | "$v0_prime$ conflicts with $v0$ through $m0$, but we should accept this fault as it \ [INFO] [stderr] 695 | | doesnt cross the fault threshold for the set, and thus the state_fault_weight should \ [INFO] [stderr] 696 | | be incremented to 1.0" [INFO] [stderr] 697 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 32 ~ [INFO] [stderr] 33 | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | $lhs, $rhs, $message [INFO] [stderr] 35 ~ , [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:32:13 [INFO] [stderr] | [INFO] [stderr] 32 | / format!( [INFO] [stderr] 33 | | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | | $lhs, $rhs, $message [INFO] [stderr] 35 | | ), [INFO] [stderr] | |_____________^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:731:9 [INFO] [stderr] | [INFO] [stderr] 731 | / float_eq!( [INFO] [stderr] 732 | | state.fault_weight(), [INFO] [stderr] 733 | | 0.1, [INFO] [stderr] 734 | | "$v0_prime$ conflicts with $v0$ through $m0$, and we should NOT accept this fault as \ [INFO] [stderr] 735 | | the fault threshold gets crossed for the set, and thus the state_fault_weight should \ [INFO] [stderr] 736 | | not be incremented" [INFO] [stderr] 737 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 32 ~ [INFO] [stderr] 33 | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | $lhs, $rhs, $message [INFO] [stderr] 35 ~ , [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:32:13 [INFO] [stderr] | [INFO] [stderr] 32 | / format!( [INFO] [stderr] 33 | | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | | $lhs, $rhs, $message [INFO] [stderr] 35 | | ), [INFO] [stderr] | |_____________^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:768:9 [INFO] [stderr] | [INFO] [stderr] 768 | / float_eq!( [INFO] [stderr] 769 | | state.fault_weight(), [INFO] [stderr] 770 | | 2.0, [INFO] [stderr] 771 | | "$v0_prime$ conflict with $v0$ through $m0$, but we should NOT accept this fault as \ [INFO] [stderr] 772 | | we can't know the weight of the validator, which could be Infinity, and thus the \ [INFO] [stderr] 773 | | state_fault_weight should be unchanged" [INFO] [stderr] 774 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 32 ~ [INFO] [stderr] 33 | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | $lhs, $rhs, $message [INFO] [stderr] 35 ~ , [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:32:13 [INFO] [stderr] | [INFO] [stderr] 32 | / format!( [INFO] [stderr] 33 | | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | | $lhs, $rhs, $message [INFO] [stderr] 35 | | ), [INFO] [stderr] | |_____________^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:809:9 [INFO] [stderr] | [INFO] [stderr] 809 | / float_eq!( [INFO] [stderr] 810 | | state.fault_weight(), [INFO] [stderr] 811 | | 1.0, [INFO] [stderr] 812 | | "$v0_prime$ conflict with $v0$ through $m0$, but we should NOT accept this fault as \ [INFO] [stderr] 813 | | we can't know the weight of the validator, which could be Infinity, and thus the \ [INFO] [stderr] 814 | | state_fault_weight should be unchanged" [INFO] [stderr] 815 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 32 ~ [INFO] [stderr] 33 | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | $lhs, $rhs, $message [INFO] [stderr] 35 ~ , [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:845:9 [INFO] [stderr] | [INFO] [stderr] 845 | float_eq!(validator_state.fault_weight(), 1.0); [INFO] [stderr] | ---------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:877:9 [INFO] [stderr] | [INFO] [stderr] 877 | / float_eq!( [INFO] [stderr] 878 | | validator_state.validators_weights().weight(&0).unwrap(), [INFO] [stderr] 879 | | 0.0 [INFO] [stderr] 880 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/justification.rs:881:9 [INFO] [stderr] | [INFO] [stderr] 881 | float_eq!(validator_state.fault_weight(), 0.0); [INFO] [stderr] | ---------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/validator.rs:459:9 [INFO] [stderr] | [INFO] [stderr] 459 | float_eq!(weights.weight(&0).unwrap(), 1.0); [INFO] [stderr] | ------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/validator.rs:460:9 [INFO] [stderr] | [INFO] [stderr] 460 | float_eq!(weights.weight(&1).unwrap(), -1.0); [INFO] [stderr] | -------------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/validator.rs:483:9 [INFO] [stderr] | [INFO] [stderr] 483 | / float_eq!( [INFO] [stderr] 484 | | weights.sum_weight_validators(&HashSet::from_iter(vec![0, 1])), [INFO] [stderr] 485 | | 0.0 [INFO] [stderr] 486 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/validator.rs:487:9 [INFO] [stderr] | [INFO] [stderr] 487 | / float_eq!( [INFO] [stderr] 488 | | weights.sum_weight_validators(&HashSet::from_iter(vec![0, 2])), [INFO] [stderr] 489 | | 4.3 [INFO] [stderr] 490 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:26:13 [INFO] [stderr] | [INFO] [stderr] 26 | format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/validator.rs:500:9 [INFO] [stderr] | [INFO] [stderr] 500 | / float_eq!( [INFO] [stderr] 501 | | weights.sum_all_weights(), [INFO] [stderr] 502 | | weights.sum_weight_validators(&HashSet::from_iter(vec![0, 2])) [INFO] [stderr] 503 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 26 - format!("float_eq: {} and {} aren't equal", $lhs, $rhs), [INFO] [stderr] 26 + "float_eq: {} and {} aren't equal", $lhs, $rhs, [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:32:13 [INFO] [stderr] | [INFO] [stderr] 32 | / format!( [INFO] [stderr] 33 | | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | | $lhs, $rhs, $message [INFO] [stderr] 35 | | ), [INFO] [stderr] | |_____________^ [INFO] [stderr] | [INFO] [stderr] ::: src/validator.rs:543:9 [INFO] [stderr] | [INFO] [stderr] 543 | / float_eq!( [INFO] [stderr] 544 | | validator_state.fault_weight(), [INFO] [stderr] 545 | | 0.0, [INFO] [stderr] 546 | | "fault weight should be 0" [INFO] [stderr] 547 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stdout] [INFO] [stderr] 32 ~ [INFO] [stdout] running 69 tests [INFO] [stderr] 33 | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | $lhs, $rhs, $message [INFO] [stderr] 35 ~ , [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:32:13 [INFO] [stderr] | [INFO] [stderr] 32 | / format!( [INFO] [stderr] 33 | | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | | $lhs, $rhs, $message [INFO] [stderr] 35 | | ), [INFO] [stderr] | |_____________^ [INFO] [stderr] | [INFO] [stderr] ::: src/validator.rs:596:9 [INFO] [stderr] | [INFO] [stderr] 596 | / float_eq!( [INFO] [stderr] 597 | | validator_state.fault_weight(), [INFO] [stderr] 598 | | 1.0, [INFO] [stderr] 599 | | "fault weight should be 1" [INFO] [stderr] 600 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stderr] 32 ~ [INFO] [stderr] 33 | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | $lhs, $rhs, $message [INFO] [stderr] 35 ~ , [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: panic message is not a string literal [INFO] [stderr] --> src/tests_common/utils.rs:32:13 [INFO] [stderr] | [INFO] [stderr] 32 | / format!( [INFO] [stderr] 33 | | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stderr] 34 | | $lhs, $rhs, $message [INFO] [stderr] 35 | | ), [INFO] [stderr] | |_____________^ [INFO] [stderr] | [INFO] [stderr] ::: src/validator.rs:649:9 [INFO] [stderr] | [INFO] [stderr] 649 | / float_eq!( [INFO] [stderr] 650 | | validator_state.fault_weight(), [INFO] [stderr] 651 | | 0.0, [INFO] [stderr] 652 | | "fault weight should be 0" [INFO] [stderr] 653 | | ); [INFO] [stderr] | |_________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stderr] = note: for more information, see [INFO] [stderr] = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here [INFO] [stderr] = note: this warning originates in the macro `float_eq` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] help: remove the `format!(..)` macro call [INFO] [stderr] | [INFO] [stdout] test blockchain::tests::best_children_empty ... ok [INFO] [stderr] 32 ~ [INFO] [stdout] test blockchain::tests::from_prevblock_message_none ... ok [INFO] [stderr] 33 | "float_eq: {} and {} aren't equal. Provided message: {}", [INFO] [stdout] test blockchain::tests::children_missing_children_are_not_included ... ok [INFO] [stderr] 34 | $lhs, $rhs, $message [INFO] [stdout] test blockchain::tests::from_prevblock_message ... ok [INFO] [stderr] 35 ~ , [INFO] [stdout] test blockchain::tests::from_message ... ok [INFO] [stderr] | [INFO] [stdout] test blockchain::tests::children ... ok [INFO] [stderr] [INFO] [stdout] test blockchain::tests::best_children_trivial ... ok [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] test blockchain::tests::parse_blockchains ... ok [INFO] [stderr] --> tests/common/binary.rs:28:45 [INFO] [stderr] | [INFO] [stderr] 28 | #[derive(Clone, Eq, PartialEq, Debug, Hash, serde_derive::Serialize)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand` [INFO] [stderr] = 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] [stderr] = help: try referring to `serde_derive::Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> tests/common/binary.rs:28:45 [INFO] [stderr] | [INFO] [stderr] 28 | #[derive(Clone, Eq, PartialEq, Debug, Hash, serde_derive::Serialize)] [INFO] [stderr] | ^---------------------- [INFO] [stderr] | | [INFO] [stderr] | `Serialize` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_BoolWrapper` [INFO] [stderr] 29 | pub struct BoolWrapper(pub bool); [INFO] [stderr] | ----------- `BoolWrapper` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `serde_derive::Serialize` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = 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] [stderr] = 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] [stderr] = 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] [stderr] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `serde_derive::Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> examples/serde.rs:33:10 [INFO] [stderr] | [INFO] [stderr] 33 | #[derive(Serialize, Deserialize, PartialEq, Debug)] [INFO] [stderr] | ^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand` [INFO] [stderr] = 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] [stderr] = help: try referring to `Serialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> examples/serde.rs:33:21 [INFO] [stderr] | [INFO] [stderr] 33 | #[derive(Serialize, Deserialize, PartialEq, Debug)] [INFO] [stderr] | ^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `integration_test`, `proptest`, and `rand` [INFO] [stderr] = 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] [stderr] = help: try referring to `Deserialize` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> examples/serde.rs:33:10 [INFO] [stderr] | [INFO] [stderr] 33 | #[derive(Serialize, Deserialize, PartialEq, Debug)] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Serialize` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_SERIALIZE_FOR_Example` [INFO] [stderr] 34 | struct Example { [INFO] [stderr] | ------- `Example` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Serialize` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = 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] [stderr] = 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] [stderr] = 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] [stderr] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> examples/serde.rs:33:21 [INFO] [stderr] | [INFO] [stderr] 33 | #[derive(Serialize, Deserialize, PartialEq, Debug)] [INFO] [stderr] | ^---------- [INFO] [stderr] | | [INFO] [stderr] | `Deserialize` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_DESERIALIZE_FOR_Example` [INFO] [stderr] 34 | struct Example { [INFO] [stderr] | ------- `Example` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Deserialize` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = 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] [stderr] = 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] [stderr] = 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] [stderr] = note: this warning originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `core_cbc_casper` (example "ternary") generated 2 warnings [INFO] [stderr] warning: `core_cbc_casper` (lib test) generated 43 warnings (20 duplicates) (run `cargo fix --lib -p core_cbc_casper --tests` to apply 23 suggestions) [INFO] [stderr] warning: `core_cbc_casper` (test "binary") generated 2 warnings [INFO] [stderr] warning: `core_cbc_casper` (example "serde") generated 4 warnings [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.19s [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 1` [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/core_cbc_casper-5eee008fde177371) [INFO] [stdout] test blockchain::tests::is_member_ancestor ... ok [INFO] [stdout] test blockchain::tests::is_member_self ... ok [INFO] [stdout] test blockchain::tests::ncestor ... ok [INFO] [stdout] test justification::test::from_messages ... ok [INFO] [stdout] test justification::test::from_messages_duplicate ... ok [INFO] [stdout] test justification::test::equivocate ... ok [INFO] [stdout] test justification::test::faulty_insert_sorted ... ok [INFO] [stdout] test justification::test::faulty_inserts ... ok [INFO] [stdout] test justification::test::faulty_insert_double_equivocation ... ok [INFO] [stdout] test justification::test::faulty_insert_accept_fault ... ok [INFO] [stdout] test justification::test::faulty_insert_with_slash ... ok [INFO] [stdout] test justification::test::faulty_insert_at_threshold ... ok [INFO] [stdout] test justification::test::faulty_insert_accept_with_bigger_numbers ... ok [INFO] [stdout] test justification::test::justification_make_estimate ... ok [INFO] [stdout] test justification::test::justification_make_estimate_equivocator_at_threshold ... ok [INFO] [stdout] test justification::test::justification_make_estimate_equivocator_not_at_threshold ... ok [INFO] [stdout] test justification::test::latest_messages_update_new_message ... ok [INFO] [stdout] test justification::test::latest_messages_update_duplicate_message ... ok [INFO] [stdout] test justification::test::latest_messages_update_equivocation ... ok [INFO] [stdout] test message::test::from_validator_state ... ok [INFO] [stdout] test justification::test::latest_messages_update_new_sender ... ok [INFO] [stdout] test message::test::from_validator_state_duplicates ... ok [INFO] [stdout] test message::test::from_validator_state_equivocator ... ok [INFO] [stdout] test message::test::from_validator_state_only_equivocations ... ok [INFO] [stdout] test message::test::from_validator_state_equivocator_at_threshhold ... ok [INFO] [stdout] test message::test::message_depends ... ok [INFO] [stdout] test blockchain::tests::best_children_tie ... ok [INFO] [stdout] test message::test::message_equality ... ok [INFO] [stdout] test blockchain::tests::best_children_indirect ... ok [INFO] [stdout] test blockchain::tests::score ... ok [INFO] [stdout] test message::test::message_equivocates ... ok [INFO] [stdout] test blockchain::tests::ghost_tie ... ok [INFO] [stdout] test message::test::message_equivocates_indirect_direct_equivocation ... ok [INFO] [stdout] test util::weight::tests::addition ... ok [INFO] [stdout] test util::weight::tests::greater ... ok [INFO] [stdout] test util::weight::tests::substraction ... ok [INFO] [stdout] test message::test::message_equivocates_indirect_semi_direct ... ok [INFO] [stdout] test message::test::message_equivocates_indirect_total_indirection ... ok [INFO] [stdout] test validator::tests::validator_state_update_equivocate_at_threshold ... ok [INFO] [stdout] test validator::tests::state_sort_by_faultweight_unknown_equivocators ... ok [INFO] [stdout] test util::weight::tests::smaller ... ok [INFO] [stdout] test validator::tests::validator_state_update ... ok [INFO] [stdout] test validator::tests::state_sort_by_faultweight_known_equivocators ... ok [INFO] [stdout] test validator::tests::state_sort_by_faultweight_no_fault ... ok [INFO] [stdout] test justification::test::faulty_insert_unknown_weights ... ok [INFO] [stdout] test validator::tests::validator_state_update_equivocate_under_threshold ... ok [INFO] [stdout] test util::weight::tests::equality ... ok [INFO] [stdout] test justification::test::latest_messages_update_old_message ... ok [INFO] [stdout] test message::test::message_equivocates_indirect_commutativity ... ok [INFO] [stdout] test validator::tests::weights_sum_all_weights ... ok [INFO] [stdout] test validator::tests::weights_sum_weight_validators ... ok [INFO] [stdout] test validator::tests::weights_validators_exclude_nan_weights ... ok [INFO] [stdout] test validator::tests::weights_validators_include_positive_weight ... ok [INFO] [stdout] test validator::tests::weights_weight ... ok [INFO] [stdout] test validator::tests::weights_validators_exclude_negative_weights ... ok [INFO] [stdout] test validator::tests::weights_validators_include_infinity_weighted_validators ... ok [INFO] [stdout] test validator::tests::weights_weight_not_found ... ok [INFO] [stdout] test validator::tests::weights_validators_exclude_zero_weighted_validators ... ok [INFO] [stdout] test blockchain::tests::ghost ... ok [INFO] [stdout] test justification::test::from_messages_equivocation ... ok [INFO] [stderr] Running tests/binary.rs (/opt/rustwide/target/debug/deps/binary-1e5931cb5e0afee6) [INFO] [stdout] test blockchain::tests::safety_oracles ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 69 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.09s [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 2 tests [INFO] [stdout] test equal_weight ... ok [INFO] [stdout] test vote_swaying ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s [INFO] [stdout] [INFO] [stderr] Running tests/blockchain.rs (/opt/rustwide/target/debug/deps/blockchain-629d91547b233b46) [INFO] [stdout] [INFO] [stdout] running 2 tests [INFO] [stdout] test partial_view ... ok [INFO] [stdout] test full_view ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s [INFO] [stdout] [INFO] [stderr] Running tests/generative_tests.rs (/opt/rustwide/target/debug/deps/generative_tests-4f29b7e3f22a6725) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running tests/integer.rs (/opt/rustwide/target/debug/deps/integer-583b6a2f1a33e834) [INFO] [stdout] [INFO] [stdout] running 3 tests [INFO] [stdout] test uneven_weights_1 ... ok [INFO] [stdout] test uneven_weights_4 ... ok [INFO] [stdout] test equal_weight ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s [INFO] [stdout] [INFO] [stderr] Doc-tests core_cbc_casper [INFO] [stdout] [INFO] [stdout] running 15 tests [INFO] [stdout] test src/tests_common/blockdata.rs - tests_common::blockdata::ValidatorNameBlockData (line 33) ... ok [INFO] [stdout] test src/tests_common/vote_count.rs - tests_common::vote_count::VoteCount (line 42) ... ok [INFO] [stdout] test src/util/weight.rs - util::weight::Zero (line 30) ... ok [INFO] [stdout] test src/blockchain.rs - blockchain::BlockData (line 43) ... ok [INFO] [stdout] test src/message.rs - message::Message (line 84) ... ok [INFO] [stdout] test src/util/weight.rs - util::weight::Weight (line 130) ... ok [INFO] [stdout] test src/blockchain.rs - blockchain::Block (line 108) ... ok [INFO] [stdout] test src/justification.rs - justification::Justification (line 38) ... ok [INFO] [stdout] test src/validator.rs - validator::Weights (line 294) ... ok [INFO] [stdout] test src/util/id.rs - util::id::Id (line 42) ... ok [INFO] [stdout] test src/validator.rs - validator::ValidatorName (line 42) ... ok [INFO] [stdout] test src/validator.rs - validator::State (line 84) ... ok [INFO] [stdout] test src/estimator.rs - estimator::Estimator (line 41) ... ok [INFO] [stdout] test src/justification.rs - justification::LatestMessages (line 244) ... ok [INFO] [stdout] test src/justification.rs - justification::LatestMessagesHonest (line 428) ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 15 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.19s [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "13ecb1e5dcff7cbdc8c6acb31ccc059a2b4e52df2940b4c9748ce084e345b4e4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "13ecb1e5dcff7cbdc8c6acb31ccc059a2b4e52df2940b4c9748ce084e345b4e4", kill_on_drop: false }` [INFO] [stdout] 13ecb1e5dcff7cbdc8c6acb31ccc059a2b4e52df2940b4c9748ce084e345b4e4