[INFO] fetching crate jmt 0.11.0... [INFO] testing jmt-0.11.0 against beta-2025-02-18 for beta-1.86-1 [INFO] extracting crate jmt 0.11.0 into /workspace/builds/worker-2-tc2/source [INFO] validating manifest of crates.io crate jmt 0.11.0 on toolchain beta-2025-02-18 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-02-18" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate jmt 0.11.0 [INFO] finished tweaking crates.io crate jmt 0.11.0 [INFO] tweaked toml for crates.io crate jmt 0.11.0 written to /workspace/builds/worker-2-tc2/source/Cargo.toml [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-02-18" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 117 packages to latest compatible versions [INFO] [stderr] Adding hashbrown v0.13.2 (available: v0.15.2) [INFO] [stderr] Adding itertools v0.10.5 (available: v0.14.0) [INFO] [stderr] Adding num-derive v0.3.3 (available: v0.4.2) [INFO] [stderr] Adding proptest-derive v0.3.0 (available: v0.5.1) [INFO] [stderr] Adding rand v0.8.5 (available: v0.9.0) [INFO] [stderr] Adding thiserror v1.0.69 (available: v2.0.11) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-02-18" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/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:3959728d45483eb673ba100a951a6b9f5012970368db2a9e08e0ac9b67c8a5ad" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-02-18" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 65fe89897240aecb4b4d0a767de98eba429c8b49cc6e37ec732846d6a01953f5 [INFO] running `Command { std: "docker" "start" "-a" "65fe89897240aecb4b4d0a767de98eba429c8b49cc6e37ec732846d6a01953f5", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "65fe89897240aecb4b4d0a767de98eba429c8b49cc6e37ec732846d6a01953f5", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "65fe89897240aecb4b4d0a767de98eba429c8b49cc6e37ec732846d6a01953f5", kill_on_drop: false }` [INFO] [stdout] 65fe89897240aecb4b4d0a767de98eba429c8b49cc6e37ec732846d6a01953f5 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:3959728d45483eb673ba100a951a6b9f5012970368db2a9e08e0ac9b67c8a5ad" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-02-18" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 52b4188f492641716752fdb948b642c1766dd159e47423c5ec245c8f133247ba [INFO] running `Command { std: "docker" "start" "-a" "52b4188f492641716752fdb948b642c1766dd159e47423c5ec245c8f133247ba", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.93 [INFO] [stderr] Compiling unicode-ident v1.0.17 [INFO] [stderr] Compiling version_check v0.9.5 [INFO] [stderr] Compiling typenum v1.18.0 [INFO] [stderr] Compiling subtle v2.6.1 [INFO] [stderr] Compiling once_cell v1.20.3 [INFO] [stderr] Compiling shlex v1.3.0 [INFO] [stderr] Compiling equivalent v1.0.2 [INFO] [stderr] Compiling hashbrown v0.15.2 [INFO] [stderr] Compiling cfg-if v1.0.0 [INFO] [stderr] Compiling anyhow v1.0.96 [INFO] [stderr] Compiling cc v1.2.15 [INFO] [stderr] Compiling toml_datetime v0.6.8 [INFO] [stderr] Compiling winnow v0.7.3 [INFO] [stderr] Compiling generic-array v0.14.7 [INFO] [stderr] Compiling serde v1.0.218 [INFO] [stderr] Compiling either v1.14.0 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Compiling indexmap v2.7.1 [INFO] [stderr] Compiling itertools v0.14.0 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling quote v1.0.38 [INFO] [stderr] Compiling cfg_aliases v0.2.1 [INFO] [stderr] Compiling autocfg v1.4.0 [INFO] [stderr] Compiling borsh v1.5.5 [INFO] [stderr] Compiling syn v2.0.98 [INFO] [stderr] Compiling arrayref v0.3.9 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling base64 v0.21.7 [INFO] [stderr] Compiling crypto-common v0.1.6 [INFO] [stderr] Compiling block-buffer v0.10.4 [INFO] [stderr] Compiling arrayvec v0.7.6 [INFO] [stderr] Compiling digest v0.10.7 [INFO] [stderr] Compiling zerocopy v0.7.35 [INFO] [stderr] Compiling cpufeatures v0.2.17 [INFO] [stderr] Compiling bytes v1.10.0 [INFO] [stderr] Compiling blake3 v1.6.0 [INFO] [stderr] Compiling keccak v0.1.5 [INFO] [stderr] Compiling constant_time_eq v0.3.1 [INFO] [stderr] Compiling toml_edit v0.22.24 [INFO] [stderr] Compiling sha3 v0.10.8 [INFO] [stderr] Compiling sha2 v0.10.8 [INFO] [stderr] Compiling ripemd v0.1.3 [INFO] [stderr] Compiling blake2 v0.10.6 [INFO] [stderr] Compiling tracing-core v0.1.33 [INFO] [stderr] Compiling pin-project-lite v0.2.16 [INFO] [stderr] Compiling hex v0.4.3 [INFO] [stderr] Compiling itertools v0.10.5 [INFO] [stderr] Compiling hashbrown v0.13.2 [INFO] [stderr] Compiling mirai-annotations v1.12.0 [INFO] [stderr] Compiling proc-macro-crate v3.2.0 [INFO] [stderr] Compiling num-derive v0.3.3 [INFO] [stderr] Compiling serde_derive v1.0.218 [INFO] [stderr] Compiling prost-derive v0.13.5 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling tracing-attributes v0.1.28 [INFO] [stderr] Compiling borsh-derive v1.5.5 [INFO] [stderr] Compiling tracing v0.1.41 [INFO] [stderr] Compiling prost v0.13.5 [INFO] [stderr] Compiling informalsystems-pbjson v0.7.0 [INFO] [stderr] Compiling ics23 v0.12.0 [INFO] [stderr] Compiling jmt v0.11.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | assume!(index < 32 * 2); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [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 macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:85:9 [INFO] [stdout] | [INFO] [stdout] 85 | assume!(index < self.pos.end); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:86:9 [INFO] [stdout] | [INFO] [stdout] 86 | assume!(self.hash_bytes.len() == 32); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:87:9 [INFO] [stdout] | [INFO] [stdout] 87 | assume!(self.pos.end == self.hash_bytes.len() * 8); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:102:9 [INFO] [stdout] | [INFO] [stdout] 102 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:112:9 [INFO] [stdout] | [INFO] [stdout] 112 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:186:9 [INFO] [stdout] | [INFO] [stdout] 186 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:283:9 [INFO] [stdout] | [INFO] [stdout] 283 | precondition!(start <= end); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:284:9 [INFO] [stdout] | [INFO] [stdout] 284 | precondition!(start <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:285:9 [INFO] [stdout] | [INFO] [stdout] 285 | precondition!(end <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:295:9 [INFO] [stdout] | [INFO] [stdout] 295 | assume!(self.start <= self.pos.start); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:296:9 [INFO] [stdout] | [INFO] [stdout] 296 | assume!(self.pos.start <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:302:9 [INFO] [stdout] | [INFO] [stdout] 302 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:303:9 [INFO] [stdout] | [INFO] [stdout] 303 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:309:9 [INFO] [stdout] | [INFO] [stdout] 309 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:310:9 [INFO] [stdout] | [INFO] [stdout] 310 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:327:9 [INFO] [stdout] | [INFO] [stdout] 327 | assume!(self.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/restore.rs:83:9 [INFO] [stdout] | [INFO] [stdout] 83 | precondition!(index < 16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: associated function `from_bit_iter` is never used [INFO] [stdout] --> src/bytes32ext.rs:19:8 [INFO] [stdout] | [INFO] [stdout] 5 | pub trait Bytes32Ext: Index + Sized { [INFO] [stdout] | ---------- associated function in this trait [INFO] [stdout] ... [INFO] [stdout] 19 | fn from_bit_iter(iter: impl ExactSizeIterator) -> Option; [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` 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/node_type.rs:869:10 [INFO] [stdout] | [INFO] [stdout] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stdout] | ^------------ [INFO] [stdout] | | [INFO] [stdout] | `FromPrimitive` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_NUM_FromPrimitive_FOR_NodeTag` [INFO] [stdout] 870 | #[borsh(use_discriminant = false)] [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ------- `NodeTag` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `FromPrimitive` (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/node_type.rs:869:25 [INFO] [stdout] | [INFO] [stdout] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stdout] | ^---------- [INFO] [stdout] | | [INFO] [stdout] | `ToPrimitive` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_NUM_ToPrimitive_FOR_NodeTag` [INFO] [stdout] 870 | #[borsh(use_discriminant = false)] [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ------- `NodeTag` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `ToPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 58.29s [INFO] running `Command { std: "docker" "inspect" "52b4188f492641716752fdb948b642c1766dd159e47423c5ec245c8f133247ba", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "52b4188f492641716752fdb948b642c1766dd159e47423c5ec245c8f133247ba", kill_on_drop: false }` [INFO] [stdout] 52b4188f492641716752fdb948b642c1766dd159e47423c5ec245c8f133247ba [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:3959728d45483eb673ba100a951a6b9f5012970368db2a9e08e0ac9b67c8a5ad" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-02-18" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] d81def72c8827d0bc5075b4f89d86a4cac4113879c11c1aba16c461bb7531408 [INFO] running `Command { std: "docker" "start" "-a" "d81def72c8827d0bc5075b4f89d86a4cac4113879c11c1aba16c461bb7531408", kill_on_drop: false }` [INFO] [stderr] Compiling libc v0.2.170 [INFO] [stderr] Compiling byteorder v1.5.0 [INFO] [stderr] Compiling zerocopy-derive v0.7.35 [INFO] [stderr] Compiling proc-macro2 v0.4.30 [INFO] [stderr] Compiling getrandom v0.3.1 [INFO] [stderr] Compiling rustix v0.38.44 [INFO] [stderr] Compiling linux-raw-sys v0.4.15 [INFO] [stderr] Compiling bitflags v2.8.0 [INFO] [stderr] Compiling unicode-xid v0.1.0 [INFO] [stderr] Compiling lock_api v0.4.12 [INFO] [stderr] Compiling parking_lot_core v0.9.10 [INFO] [stderr] Compiling fastrand v2.3.0 [INFO] [stderr] Compiling syn v0.15.44 [INFO] [stderr] Compiling hex v0.4.3 [INFO] [stderr] Compiling quick-error v1.2.3 [INFO] [stderr] Compiling scopeguard v1.2.0 [INFO] [stderr] Compiling serde_json v1.0.139 [INFO] [stderr] Compiling fnv v1.0.7 [INFO] [stderr] Compiling smallvec v1.14.0 [INFO] [stderr] Compiling bit-vec v0.8.0 [INFO] [stderr] Compiling quote v0.6.13 [INFO] [stderr] Compiling ics23 v0.12.0 [INFO] [stderr] Compiling bit-set v0.8.0 [INFO] [stderr] Compiling unarray v0.1.4 [INFO] [stderr] Compiling itoa v1.0.14 [INFO] [stderr] Compiling getrandom v0.2.15 [INFO] [stderr] Compiling wait-timeout v0.2.1 [INFO] [stderr] Compiling rand_core v0.6.4 [INFO] [stderr] Compiling regex-syntax v0.8.5 [INFO] [stderr] Compiling zerocopy v0.7.35 [INFO] [stderr] Compiling rand_xorshift v0.3.0 [INFO] [stderr] Compiling lazy_static v1.5.0 [INFO] [stderr] Compiling memchr v2.7.4 [INFO] [stderr] Compiling ryu v1.0.19 [INFO] [stderr] Compiling parking_lot v0.12.3 [INFO] [stderr] Compiling ppv-lite86 v0.2.20 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Compiling hashbrown v0.13.2 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling tempfile v3.17.1 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Compiling rusty-fork v0.3.0 [INFO] [stderr] Compiling jmt v0.11.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | assume!(index < 32 * 2); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [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 macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:85:9 [INFO] [stdout] | [INFO] [stdout] 85 | assume!(index < self.pos.end); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:86:9 [INFO] [stdout] | [INFO] [stdout] 86 | assume!(self.hash_bytes.len() == 32); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:87:9 [INFO] [stdout] | [INFO] [stdout] 87 | assume!(self.pos.end == self.hash_bytes.len() * 8); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:102:9 [INFO] [stdout] | [INFO] [stdout] 102 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:112:9 [INFO] [stdout] | [INFO] [stdout] 112 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:186:9 [INFO] [stdout] | [INFO] [stdout] 186 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:283:9 [INFO] [stdout] | [INFO] [stdout] 283 | precondition!(start <= end); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:284:9 [INFO] [stdout] | [INFO] [stdout] 284 | precondition!(start <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:285:9 [INFO] [stdout] | [INFO] [stdout] 285 | precondition!(end <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:295:9 [INFO] [stdout] | [INFO] [stdout] 295 | assume!(self.start <= self.pos.start); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:296:9 [INFO] [stdout] | [INFO] [stdout] 296 | assume!(self.pos.start <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:302:9 [INFO] [stdout] | [INFO] [stdout] 302 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:303:9 [INFO] [stdout] | [INFO] [stdout] 303 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:309:9 [INFO] [stdout] | [INFO] [stdout] 309 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:310:9 [INFO] [stdout] | [INFO] [stdout] 310 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:327:9 [INFO] [stdout] | [INFO] [stdout] 327 | assume!(self.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/restore.rs:83:9 [INFO] [stdout] | [INFO] [stdout] 83 | precondition!(index < 16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling proptest v1.6.0 [INFO] [stdout] warning: associated function `from_bit_iter` is never used [INFO] [stdout] --> src/bytes32ext.rs:19:8 [INFO] [stdout] | [INFO] [stdout] 5 | pub trait Bytes32Ext: Index + Sized { [INFO] [stdout] | ---------- associated function in this trait [INFO] [stdout] ... [INFO] [stdout] 19 | fn from_bit_iter(iter: impl ExactSizeIterator) -> Option; [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` 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/node_type.rs:869:10 [INFO] [stdout] | [INFO] [stdout] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stdout] | ^------------ [INFO] [stdout] | | [INFO] [stdout] | `FromPrimitive` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_NUM_FromPrimitive_FOR_NodeTag` [INFO] [stdout] 870 | #[borsh(use_discriminant = false)] [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ------- `NodeTag` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `FromPrimitive` (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/node_type.rs:869:25 [INFO] [stdout] | [INFO] [stdout] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stdout] | ^---------- [INFO] [stdout] | | [INFO] [stdout] | `ToPrimitive` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_NUM_ToPrimitive_FOR_NodeTag` [INFO] [stdout] 870 | #[borsh(use_discriminant = false)] [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ------- `NodeTag` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `ToPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling proptest-derive v0.3.0 [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | assume!(index < 32 * 2); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [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 macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:85:9 [INFO] [stdout] | [INFO] [stdout] 85 | assume!(index < self.pos.end); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:86:9 [INFO] [stdout] | [INFO] [stdout] 86 | assume!(self.hash_bytes.len() == 32); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:87:9 [INFO] [stdout] | [INFO] [stdout] 87 | assume!(self.pos.end == self.hash_bytes.len() * 8); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:102:9 [INFO] [stdout] | [INFO] [stdout] 102 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:112:9 [INFO] [stdout] | [INFO] [stdout] 112 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:186:9 [INFO] [stdout] | [INFO] [stdout] 186 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:283:9 [INFO] [stdout] | [INFO] [stdout] 283 | precondition!(start <= end); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:284:9 [INFO] [stdout] | [INFO] [stdout] 284 | precondition!(start <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:285:9 [INFO] [stdout] | [INFO] [stdout] 285 | precondition!(end <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:295:9 [INFO] [stdout] | [INFO] [stdout] 295 | assume!(self.start <= self.pos.start); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:296:9 [INFO] [stdout] | [INFO] [stdout] 296 | assume!(self.pos.start <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:302:9 [INFO] [stdout] | [INFO] [stdout] 302 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:303:9 [INFO] [stdout] | [INFO] [stdout] 303 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:309:9 [INFO] [stdout] | [INFO] [stdout] 309 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:310:9 [INFO] [stdout] | [INFO] [stdout] 310 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:327:9 [INFO] [stdout] | [INFO] [stdout] 327 | assume!(self.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/restore.rs:83:9 [INFO] [stdout] | [INFO] [stdout] 83 | precondition!(index < 16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (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/lib.rs:171:30 [INFO] [stdout] | [INFO] [stdout] 171 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stdout] | ^-------- [INFO] [stdout] | | [INFO] [stdout] | `Arbitrary` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_RootHash` [INFO] [stdout] 172 | pub struct RootHash(pub [u8; 32]); [INFO] [stdout] | -------- `RootHash` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/lib.rs:213:30 [INFO] [stdout] | [INFO] [stdout] 213 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stdout] | ^-------- [INFO] [stdout] | | [INFO] [stdout] | `Arbitrary` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_KeyHash` [INFO] [stdout] 214 | pub struct KeyHash(pub [u8; 32]); [INFO] [stdout] | ------- `KeyHash` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/lib.rs:229:30 [INFO] [stdout] | [INFO] [stdout] 229 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stdout] | ^-------- [INFO] [stdout] | | [INFO] [stdout] | `Arbitrary` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_ValueHash` [INFO] [stdout] ... [INFO] [stdout] 233 | pub struct ValueHash(pub [u8; 32]); [INFO] [stdout] | --------- `ValueHash` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/node_type.rs:50:30 [INFO] [stdout] | [INFO] [stdout] 50 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stdout] | ^-------- [INFO] [stdout] | | [INFO] [stdout] | `Arbitrary` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_NodeKey` [INFO] [stdout] 51 | pub struct NodeKey { [INFO] [stdout] | ------- `NodeKey` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/node_type.rs:145:30 [INFO] [stdout] | [INFO] [stdout] 145 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stdout] | ^-------- [INFO] [stdout] | | [INFO] [stdout] | `Arbitrary` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_Child` [INFO] [stdout] 146 | pub struct Child { [INFO] [stdout] | ----- `Child` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/node_type.rs:869:10 [INFO] [stdout] | [INFO] [stdout] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stdout] | ^------------ [INFO] [stdout] | | [INFO] [stdout] | `FromPrimitive` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_NUM_FromPrimitive_FOR_NodeTag` [INFO] [stdout] 870 | #[borsh(use_discriminant = false)] [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ------- `NodeTag` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `FromPrimitive` (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/node_type.rs:869:25 [INFO] [stdout] | [INFO] [stdout] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stdout] | ^---------- [INFO] [stdout] | | [INFO] [stdout] | `ToPrimitive` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_NUM_ToPrimitive_FOR_NodeTag` [INFO] [stdout] 870 | #[borsh(use_discriminant = false)] [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ------- `NodeTag` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `ToPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `ToPrimitive` (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/types/proof.rs:26:47 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg_attr(all(test, feature = "std"), derive(Arbitrary))] [INFO] [stdout] | ^-------- [INFO] [stdout] | | [INFO] [stdout] | `Arbitrary` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_SparseMerkleNode` [INFO] [stdout] ... [INFO] [stdout] 38 | pub(crate) enum SparseMerkleNode { [INFO] [stdout] | ---------------- `SparseMerkleNode` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/types/proof.rs:60:47 [INFO] [stdout] | [INFO] [stdout] 60 | #[cfg_attr(all(test, feature = "std"), derive(Arbitrary))] [INFO] [stdout] | ^-------- [INFO] [stdout] | | [INFO] [stdout] | `Arbitrary` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_SparseMerkleInternalNode` [INFO] [stdout] 61 | pub(crate) struct SparseMerkleInternalNode { [INFO] [stdout] | ------------------------ `SparseMerkleInternalNode` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/writer.rs:104:30 [INFO] [stdout] | [INFO] [stdout] 104 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stdout] | ^-------- [INFO] [stdout] | | [INFO] [stdout] | `Arbitrary` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_StaleNodeIndex` [INFO] [stdout] 105 | pub struct StaleNodeIndex { [INFO] [stdout] | -------------- `StaleNodeIndex` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 51.71s [INFO] running `Command { std: "docker" "inspect" "d81def72c8827d0bc5075b4f89d86a4cac4113879c11c1aba16c461bb7531408", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "d81def72c8827d0bc5075b4f89d86a4cac4113879c11c1aba16c461bb7531408", kill_on_drop: false }` [INFO] [stdout] d81def72c8827d0bc5075b4f89d86a4cac4113879c11c1aba16c461bb7531408 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:3959728d45483eb673ba100a951a6b9f5012970368db2a9e08e0ac9b67c8a5ad" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-02-18" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] f0304edcdd2718679004df140375db63b64056dc77be727ca4ccaae68762730a [INFO] running `Command { std: "docker" "start" "-a" "f0304edcdd2718679004df140375db63b64056dc77be727ca4ccaae68762730a", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/bytes32ext.rs:43:9 [INFO] [stderr] | [INFO] [stderr] 43 | assume!(index < 32 * 2); // assumed precondition [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [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 macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/bytes32ext.rs:85:9 [INFO] [stderr] | [INFO] [stderr] 85 | assume!(index < self.pos.end); // assumed precondition [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/bytes32ext.rs:86:9 [INFO] [stderr] | [INFO] [stderr] 86 | assume!(self.hash_bytes.len() == 32); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/bytes32ext.rs:87:9 [INFO] [stderr] | [INFO] [stderr] 87 | assume!(self.pos.end == self.hash_bytes.len() * 8); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:102:9 [INFO] [stderr] | [INFO] [stderr] 102 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:112:9 [INFO] [stderr] | [INFO] [stderr] 112 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:177:9 [INFO] [stderr] | [INFO] [stderr] 177 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:186:9 [INFO] [stderr] | [INFO] [stderr] 186 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:283:9 [INFO] [stderr] | [INFO] [stderr] 283 | precondition!(start <= end); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:284:9 [INFO] [stderr] | [INFO] [stderr] 284 | precondition!(start <= ROOT_NIBBLE_HEIGHT); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:285:9 [INFO] [stderr] | [INFO] [stderr] 285 | precondition!(end <= ROOT_NIBBLE_HEIGHT); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:295:9 [INFO] [stderr] | [INFO] [stderr] 295 | assume!(self.start <= self.pos.start); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:296:9 [INFO] [stderr] | [INFO] [stderr] 296 | assume!(self.pos.start <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:302:9 [INFO] [stderr] | [INFO] [stderr] 302 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:303:9 [INFO] [stderr] | [INFO] [stderr] 303 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:309:9 [INFO] [stderr] | [INFO] [stderr] 309 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:310:9 [INFO] [stderr] | [INFO] [stderr] 310 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/types/nibble/nibble_path.rs:327:9 [INFO] [stderr] | [INFO] [stderr] 327 | assume!(self.start <= self.pos.end); // invariant [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `assume` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> src/restore.rs:83:9 [INFO] [stderr] | [INFO] [stderr] 83 | precondition!(index < 16); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [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 `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: associated function `from_bit_iter` is never used [INFO] [stderr] --> src/bytes32ext.rs:19:8 [INFO] [stderr] | [INFO] [stderr] 5 | pub trait Bytes32Ext: Index + Sized { [INFO] [stderr] | ---------- associated function in this trait [INFO] [stderr] ... [INFO] [stderr] 19 | fn from_bit_iter(iter: impl ExactSizeIterator) -> Option; [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(dead_code)]` 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/node_type.rs:869:10 [INFO] [stderr] | [INFO] [stderr] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stderr] | ^------------ [INFO] [stderr] | | [INFO] [stderr] | `FromPrimitive` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_NUM_FromPrimitive_FOR_NodeTag` [INFO] [stderr] 870 | #[borsh(use_discriminant = false)] [INFO] [stderr] 871 | enum NodeTag { [INFO] [stderr] | ------- `NodeTag` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `FromPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `FromPrimitive` (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/node_type.rs:869:25 [INFO] [stderr] | [INFO] [stderr] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stderr] | ^---------- [INFO] [stderr] | | [INFO] [stderr] | `ToPrimitive` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_NUM_ToPrimitive_FOR_NodeTag` [INFO] [stderr] 870 | #[borsh(use_discriminant = false)] [INFO] [stderr] 871 | enum NodeTag { [INFO] [stderr] | ------- `NodeTag` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `ToPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `jmt` (lib) generated 22 warnings [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> src/lib.rs:171:30 [INFO] [stderr] | [INFO] [stderr] 171 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Arbitrary` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_RootHash` [INFO] [stderr] 172 | pub struct RootHash(pub [u8; 32]); [INFO] [stderr] | -------- `RootHash` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/lib.rs:213:30 [INFO] [stderr] | [INFO] [stderr] 213 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Arbitrary` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_KeyHash` [INFO] [stderr] 214 | pub struct KeyHash(pub [u8; 32]); [INFO] [stderr] | ------- `KeyHash` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/lib.rs:229:30 [INFO] [stderr] | [INFO] [stderr] 229 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Arbitrary` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_ValueHash` [INFO] [stderr] ... [INFO] [stderr] 233 | pub struct ValueHash(pub [u8; 32]); [INFO] [stderr] | --------- `ValueHash` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/node_type.rs:50:30 [INFO] [stderr] | [INFO] [stderr] 50 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Arbitrary` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_NodeKey` [INFO] [stderr] 51 | pub struct NodeKey { [INFO] [stderr] | ------- `NodeKey` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/node_type.rs:145:30 [INFO] [stderr] | [INFO] [stderr] 145 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Arbitrary` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_Child` [INFO] [stderr] 146 | pub struct Child { [INFO] [stderr] | ----- `Child` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/node_type.rs:869:10 [INFO] [stderr] | [INFO] [stderr] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stderr] | ^------------ [INFO] [stderr] | | [INFO] [stderr] | `FromPrimitive` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_NUM_FromPrimitive_FOR_NodeTag` [INFO] [stderr] 870 | #[borsh(use_discriminant = false)] [INFO] [stderr] 871 | enum NodeTag { [INFO] [stderr] | ------- `NodeTag` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `FromPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_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 `FromPrimitive` (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/types/proof.rs:26:47 [INFO] [stderr] | [INFO] [stderr] 26 | #[cfg_attr(all(test, feature = "std"), derive(Arbitrary))] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Arbitrary` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_SparseMerkleNode` [INFO] [stderr] ... [INFO] [stderr] 38 | pub(crate) enum SparseMerkleNode { [INFO] [stderr] | ---------------- `SparseMerkleNode` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/types/proof.rs:60:47 [INFO] [stderr] | [INFO] [stderr] 60 | #[cfg_attr(all(test, feature = "std"), derive(Arbitrary))] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Arbitrary` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_SparseMerkleInternalNode` [INFO] [stderr] 61 | pub(crate) struct SparseMerkleInternalNode { [INFO] [stderr] | ------------------------ `SparseMerkleInternalNode` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (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/writer.rs:104:30 [INFO] [stderr] | [INFO] [stderr] 104 | #[cfg_attr(any(test), derive(Arbitrary))] [INFO] [stderr] | ^-------- [INFO] [stderr] | | [INFO] [stderr] | `Arbitrary` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_IMPL_ARBITRARY_FOR_StaleNodeIndex` [INFO] [stderr] 105 | pub struct StaleNodeIndex { [INFO] [stderr] | -------------- `StaleNodeIndex` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Arbitrary` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Arbitrary` may come from an old version of the `proptest_derive` crate, try updating your dependency with `cargo update -p proptest_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 `Arbitrary` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `jmt` (lib test) generated 29 warnings (20 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.19s [INFO] [stdout] [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/jmt-71ad6ebefe5b22e0) [INFO] [stdout] running 84 tests [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_clairvoyant_construction_matches_interleaved_construction_small ... ok [INFO] [stdout] test tests::iterator::test_iterator_same_version ... ok [INFO] [stdout] test tests::iterator::test_long_path ... ok [INFO] [stdout] test tests::iterator::test_iterator_multiple_versions ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_1000_keys ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_batch_insertion ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_delete_then_get_in_one ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_insert_at_leaf_with_internal_created ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_insert_at_leaf_with_multiple_internals_created ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_insert_to_empty_tree ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_missing_root ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_non_batch_empty_write_set ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_non_existence ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_put_value_sets ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_two_gets_then_delete ... ok [INFO] [stdout] test tests::nibble_path::test_bit_iter ... ok [INFO] [stdout] test tests::nibble_path::test_create_nibble_path_failure - should panic ... ok [INFO] [stdout] test tests::nibble_path::test_create_nibble_path_success ... ok [INFO] [stdout] test tests::nibble_path::test_empty_nibble_path - should panic ... ok [INFO] [stdout] test tests::nibble_path::test_get_bit ... ok [INFO] [stdout] test tests::nibble_path::test_get_nibble ... ok [INFO] [stdout] test tests::nibble_path::test_last ... ok [INFO] [stdout] test tests::nibble_path::test_nibble_iter_roundtrip ... ok [INFO] [stdout] test tests::nibble_path::test_nibble_iter_to_bit_iter ... ok [INFO] [stdout] test tests::nibble_path::test_nibble_iterator ... ok [INFO] [stdout] test tests::nibble_path::test_nibble_path_fmt ... ok [INFO] [stdout] test tests::nibble_path::test_pop ... ok [INFO] [stdout] test tests::nibble_path::test_push ... ok [INFO] [stdout] test tests::nibble_path::test_skip_common_prefix ... ok [INFO] [stdout] test tests::nibble_path::test_visited_and_remaining_nibbles ... ok [INFO] [stdout] test tests::nibble_path::test_visited_nibble_iter ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::test_1000_versions ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_with_proof_with_distinct_last_nibble ... ok [INFO] [stdout] test tests::node_type::test_internal_hash_and_proof ... ok [INFO] [stdout] test tests::node_type::test_internal_node_roundtrip ... ok [INFO] [stdout] test tests::node_type::test_internal_validity ... ok [INFO] [stdout] test tests::node_type::test_leaf_hash ... ok [INFO] [stdout] test tests::node_type::test_get_child_with_siblings - should panic ... ok [INFO] [stdout] test tests::node_type::three_leaves_test1 ... ok [INFO] [stdout] test tests::node_type::two_leaves_test1 ... ok [INFO] [stdout] test tests::node_type::two_leaves_test2 ... ok [INFO] [stdout] test tests::node_type::mixed_nodes_test ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_clairvoyant_construction_matches_interleaved_construction has been running for over 60 seconds [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_leaf_count has been running for over 60 seconds [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_range_proof has been running for over 60 seconds [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_with_proof has been running for over 60 seconds [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_with_proof_with_deletions has been running for over 60 seconds [INFO] [stdout] test tests::restore::test_restore_with_interruption_sha256 ... ok [INFO] [stdout] test tests::tree_cache::test_freeze_with_delete ... ok [INFO] [stdout] test tests::tree_cache::test_get_node ... ok [INFO] [stdout] test tests::tree_cache::test_pre_genesis ... ok [INFO] [stdout] test tests::tree_cache::test_root_node ... ok [INFO] [stdout] test tests::restore::test_overwrite_sha256 has been running for over 60 seconds [INFO] [stdout] test tests::restore::test_restore_without_interruption_sha256 has been running for over 60 seconds [INFO] [stdout] test tests::restore::test_restore_without_interruption_sha256 ... ok [INFO] [stdout] test tests::update_proof::proptest_clairvoyant_construction_matches_interleaved_construction_small_proved ... ok [INFO] [stdout] test tests::update_proof::proptest_clairvoyant_construction_matches_interleaved_construction_proved has been running for over 60 seconds [INFO] [stdout] test tests::update_proof::test_1000_keys ... ok [INFO] [stdout] test tests::restore::test_overwrite_sha256 ... ok [INFO] [stdout] test tests::update_proof::test_delete_complex ... ok [INFO] [stdout] test tests::update_proof::test_delete_empty ... ok [INFO] [stdout] test tests::update_proof::test_delete_key_twice ... ok [INFO] [stdout] test tests::update_proof::test_delete_simple ... ok [INFO] [stdout] test tests::update_proof::test_delete_simple2 ... ok [INFO] [stdout] test tests::update_proof::test_delete_with_internal_sibling ... ok [INFO] [stdout] test tests::update_proof::test_gets_then_delete_with_proof ... ok [INFO] [stdout] test tests::update_proof::test_multi_deletes_after_inserts ... ok [INFO] [stdout] test tests::update_proof::test_prove_complex_insertion ... ok [INFO] [stdout] test tests::update_proof::test_prove_insertion_separate ... ok [INFO] [stdout] test tests::update_proof::test_prove_multiple_insertions ... ok [INFO] [stdout] test tests::update_proof::test_prove_update ... ok [INFO] [stdout] test tests::update_proof::test_update_proof ... ok [INFO] [stdout] test tests::vectors::test_with_vectors ... ok [INFO] [stdout] test tests::update_proof::test_1000_versions ... ok [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_existence ... ok [INFO] [stdout] test tree::ics23_impl::tests::test_ics23_bounding_path_simple has been running for over 60 seconds [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_existence_random_keys has been running for over 60 seconds [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_existence_random_keys ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_clairvoyant_construction_matches_interleaved_construction ... ok [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_nonexistence_simple ... ok [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_nonexistence_simple_large ... ok [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_nonexistence_simple_transparent ... ok [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_nonexistence_single_empty_key - should panic ... ok [INFO] [stdout] test types::proof::definition::serialization_tests::test_sparse_merkle_proof_roundtrip_borsh ... ok [INFO] [stdout] test types::proof::definition::serialization_tests::test_sparse_merkle_proof_roundtrip_serde ... ok [INFO] [stdout] test types::proof::definition::serialization_tests::test_sparse_merkle_range_proof_roundtrip_borsh ... ok [INFO] [stdout] test types::proof::definition::serialization_tests::test_sparse_merkle_range_proof_roundtrip_serde ... ok [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_nonexistence has been running for over 60 seconds [INFO] [stdout] test tree::ics23_impl::tests::test_jmt_ics23_nonexistence ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_leaf_count ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_range_proof ... ok [INFO] [stdout] test tests::update_proof::proptest_clairvoyant_construction_matches_interleaved_construction_proved ... ok [INFO] [stdout] test tree::ics23_impl::tests::test_ics23_bounding_path_simple ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_with_proof ... ok [INFO] [stdout] test tests::jellyfish_merkle::sha256_tests::proptest_get_with_proof_with_deletions ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 84 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 813.06s [INFO] [stdout] [INFO] [stderr] Doc-tests jmt [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] running `Command { std: "docker" "inspect" "f0304edcdd2718679004df140375db63b64056dc77be727ca4ccaae68762730a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "f0304edcdd2718679004df140375db63b64056dc77be727ca4ccaae68762730a", kill_on_drop: false }` [INFO] [stdout] f0304edcdd2718679004df140375db63b64056dc77be727ca4ccaae68762730a