[INFO] fetching crate diem-crypto 0.0.3... [INFO] testing diem-crypto-0.0.3 against try#b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b for pr-145330-1 [INFO] extracting crate diem-crypto 0.0.3 into /workspace/builds/worker-5-tc2/source [INFO] started tweaking crates.io crate diem-crypto 0.0.3 [INFO] finished tweaking crates.io crate diem-crypto 0.0.3 [INFO] tweaked toml for crates.io crate diem-crypto 0.0.3 written to /workspace/builds/worker-5-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate diem-crypto 0.0.3 on toolchain b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 168 packages to latest compatible versions [INFO] [stderr] Adding aes-gcm v0.8.0 (available: v0.10.3) [INFO] [stderr] Adding bitvec v0.19.6 (available: v1.0.1) [INFO] [stderr] Adding criterion v0.3.6 (available: v0.7.0) [INFO] [stderr] Adding digest v0.9.0 (available: v0.10.7) [INFO] [stderr] Adding hkdf v0.10.0 (available: v0.12.4) [INFO] [stderr] Adding proptest-derive v0.3.0 (available: v0.6.0) [INFO] [stderr] Adding rand v0.8.5 (available: v0.9.2) [INFO] [stderr] Adding rand_core v0.6.4 (available: v0.9.3) [INFO] [stderr] Adding ripemd160 v0.9.1 (available: v0.10.0) [INFO] [stderr] Adding serde-name v0.1.2 (available: v0.2.1) [INFO] [stderr] Adding sha2 v0.9.9 (available: v0.10.9) [INFO] [stderr] Adding sha3 v0.9.1 (available: v0.10.8) [INFO] [stderr] Adding subtle v2.4.1 (available: v2.6.1) [INFO] [stderr] Adding thiserror v1.0.69 (available: v2.0.17) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 28dce21e4c063841818bd8ae479b74ac0dcc6e341b3c1cf3db08bf99c42facbb [INFO] running `Command { std: "docker" "start" "-a" "28dce21e4c063841818bd8ae479b74ac0dcc6e341b3c1cf3db08bf99c42facbb", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "28dce21e4c063841818bd8ae479b74ac0dcc6e341b3c1cf3db08bf99c42facbb", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "28dce21e4c063841818bd8ae479b74ac0dcc6e341b3c1cf3db08bf99c42facbb", kill_on_drop: false }` [INFO] [stdout] 28dce21e4c063841818bd8ae479b74ac0dcc6e341b3c1cf3db08bf99c42facbb [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 8609cea7423e4eb8f3deb0291e7d0ef76d2a3e4fb514284daff70ef76967f123 [INFO] running `Command { std: "docker" "start" "-a" "8609cea7423e4eb8f3deb0291e7d0ef76d2a3e4fb514284daff70ef76967f123", kill_on_drop: false }` [INFO] [stderr] Compiling subtle v2.4.1 [INFO] [stderr] Compiling opaque-debug v0.3.1 [INFO] [stderr] Compiling fiat-crypto v0.1.20 [INFO] [stderr] Compiling cpuid-bool v0.2.0 [INFO] [stderr] Compiling generic-array v0.14.7 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling byteorder v1.5.0 [INFO] [stderr] Compiling crunchy v0.2.4 [INFO] [stderr] Compiling signature v1.6.4 [INFO] [stderr] Compiling serde_bytes v0.11.19 [INFO] [stderr] Compiling tiny-keccak v2.0.2 [INFO] [stderr] Compiling mirai-annotations v1.12.0 [INFO] [stderr] Compiling syn v2.0.106 [INFO] [stderr] Compiling digest v0.9.0 [INFO] [stderr] Compiling cipher v0.2.5 [INFO] [stderr] Compiling universal-hash v0.4.1 [INFO] [stderr] Compiling crypto-mac v0.10.1 [INFO] [stderr] Compiling block-buffer v0.9.0 [INFO] [stderr] Compiling aead v0.3.2 [INFO] [stderr] Compiling polyval v0.4.5 [INFO] [stderr] Compiling sha2 v0.9.9 [INFO] [stderr] Compiling hmac v0.10.1 [INFO] [stderr] Compiling aes-soft v0.6.4 [INFO] [stderr] Compiling ctr v0.6.0 [INFO] [stderr] Compiling hkdf v0.10.0 [INFO] [stderr] Compiling ghash v0.3.1 [INFO] [stderr] Compiling aes v0.6.0 [INFO] [stderr] Compiling aes-gcm v0.8.0 [INFO] [stderr] Compiling diem-crypto-derive v0.0.3 [INFO] [stderr] Compiling serde_derive v1.0.228 [INFO] [stderr] Compiling zeroize_derive v1.4.2 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling zeroize v1.8.2 [INFO] [stderr] Compiling curve25519-dalek-fiat v0.1.0 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling x25519-dalek-fiat v0.1.0 [INFO] [stderr] Compiling serde v1.0.228 [INFO] [stderr] Compiling ed25519 v1.5.3 [INFO] [stderr] Compiling serde-name v0.1.2 [INFO] [stderr] Compiling bcs v0.1.6 [INFO] [stderr] Compiling ed25519-dalek-fiat v0.1.0 [INFO] [stderr] Compiling diem-crypto v0.0.3 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:7:13 [INFO] [stdout] | [INFO] [stdout] 7 | #![cfg_attr(mirai, allow(incomplete_features), feature(const_generics))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:25:7 [INFO] [stdout] | [INFO] [stdout] 25 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:68:11 [INFO] [stdout] | [INFO] [stdout] 68 | #[cfg(all(mirai, not(debug_assertions)))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:79:7 [INFO] [stdout] | [INFO] [stdout] 79 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:81:11 [INFO] [stdout] | [INFO] [stdout] 81 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:387:9 [INFO] [stdout] | [INFO] [stdout] 387 | add_tag!(&public_key, ValidatedPublicKeyTag); // This key has gone through validity checks. [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` 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 `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `batch` [INFO] [stdout] --> src/ed25519.rs:450:11 [INFO] [stdout] | [INFO] [stdout] 450 | #[cfg(feature = "batch")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `assert-private-keys-not-cloneable`, `cloneable-private-keys`, `default`, `fiat`, `fuzzing`, `proptest`, `proptest-derive`, `u32`, and `u64` [INFO] [stdout] = help: consider adding `batch` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:421:9 [INFO] [stdout] | [INFO] [stdout] 421 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/ed25519.rs:421:23 [INFO] [stdout] | [INFO] [stdout] 421 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/ed25519.rs:433:9 [INFO] [stdout] | [INFO] [stdout] 433 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/ed25519.rs:433:23 [INFO] [stdout] | [INFO] [stdout] 433 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/hash.rs:209:9 [INFO] [stdout] | [INFO] [stdout] 209 | assume!(index < Self::LENGTH_IN_BITS); // 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/hash.rs:217:9 [INFO] [stdout] | [INFO] [stdout] 217 | assume!(index < Self::LENGTH * 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: 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/hash.rs:435:9 [INFO] [stdout] | [INFO] [stdout] 435 | 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/hash.rs:436:9 [INFO] [stdout] | [INFO] [stdout] 436 | assume!(self.hash_bytes.len() == HashValue::LENGTH); // 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/hash.rs:437:9 [INFO] [stdout] | [INFO] [stdout] 437 | 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/multi_ed25519.rs:45:7 [INFO] [stdout] | [INFO] [stdout] 45 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/multi_ed25519.rs:47:11 [INFO] [stdout] | [INFO] [stdout] 47 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/multi_ed25519.rs:311:13 [INFO] [stdout] | [INFO] [stdout] 311 | add_tag!(&public_key, ValidatedPublicKeyTag); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` 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 `add_tag` (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/multi_ed25519.rs:489:9 [INFO] [stdout] | [INFO] [stdout] 489 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/multi_ed25519.rs:489:23 [INFO] [stdout] | [INFO] [stdout] 489 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/multi_ed25519.rs:505:9 [INFO] [stdout] | [INFO] [stdout] 505 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/multi_ed25519.rs:505:23 [INFO] [stdout] | [INFO] [stdout] 505 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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 14.91s [INFO] running `Command { std: "docker" "inspect" "8609cea7423e4eb8f3deb0291e7d0ef76d2a3e4fb514284daff70ef76967f123", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "8609cea7423e4eb8f3deb0291e7d0ef76d2a3e4fb514284daff70ef76967f123", kill_on_drop: false }` [INFO] [stdout] 8609cea7423e4eb8f3deb0291e7d0ef76d2a3e4fb514284daff70ef76967f123 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+b6ae10aa7319b7ebb6c7b3331dd71a9d6c9c5b4b" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] d8f4ed4157f9349a6aadc0574dff35d59605e332363d36e9d049c78745efb847 [INFO] running `Command { std: "docker" "start" "-a" "d8f4ed4157f9349a6aadc0574dff35d59605e332363d36e9d049c78745efb847", kill_on_drop: false }` [INFO] [stderr] Compiling serde_core v1.0.228 [INFO] [stderr] Compiling getrandom v0.3.3 [INFO] [stderr] Compiling block-padding v0.2.1 [INFO] [stderr] Compiling proc-macro2 v0.4.30 [INFO] [stderr] Compiling byteorder v1.5.0 [INFO] [stderr] Compiling rustix v1.1.2 [INFO] [stderr] Compiling bitflags v2.9.4 [INFO] [stderr] Compiling target-triple v0.1.4 [INFO] [stderr] Compiling radium v0.5.3 [INFO] [stderr] Compiling winnow v0.7.13 [INFO] [stderr] Compiling syn v0.15.44 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Compiling regex-automata v0.4.11 [INFO] [stderr] Compiling wait-timeout v0.2.1 [INFO] [stderr] Compiling csv-core v0.1.12 [INFO] [stderr] Compiling half v1.8.3 [INFO] [stderr] Compiling block-buffer v0.9.0 [INFO] [stderr] Compiling sha2 v0.9.9 [INFO] [stderr] Compiling bit-vec v0.8.0 [INFO] [stderr] Compiling criterion-plot v0.4.5 [INFO] [stderr] Compiling clap v2.34.0 [INFO] [stderr] Compiling bit-set v0.8.0 [INFO] [stderr] Compiling rand_core v0.9.3 [INFO] [stderr] Compiling funty v1.1.0 [INFO] [stderr] Compiling wyz v0.2.0 [INFO] [stderr] Compiling unarray v0.1.4 [INFO] [stderr] Compiling keccak v0.1.5 [INFO] [stderr] Compiling curve25519-dalek-fiat v0.1.0 [INFO] [stderr] Compiling ripemd160 v0.9.1 [INFO] [stderr] Compiling quote v0.6.13 [INFO] [stderr] Compiling rand v0.9.2 [INFO] [stderr] Compiling rand_xorshift v0.4.0 [INFO] [stderr] Compiling rand_chacha v0.9.0 [INFO] [stderr] Compiling sha3 v0.9.1 [INFO] [stderr] Compiling bitvec v0.19.6 [INFO] [stderr] Compiling x25519-dalek-fiat v0.1.0 [INFO] [stderr] Compiling toml_parser v1.0.3 [INFO] [stderr] Compiling regex v1.11.3 [INFO] [stderr] Compiling tempfile v3.23.0 [INFO] [stderr] Compiling rusty-fork v0.3.0 [INFO] [stderr] Compiling proptest v1.8.0 [INFO] [stderr] Compiling serde v1.0.228 [INFO] [stderr] Compiling serde_json v1.0.145 [INFO] [stderr] Compiling toml_datetime v0.7.2 [INFO] [stderr] Compiling serde_spanned v1.0.2 [INFO] [stderr] Compiling serde_bytes v0.11.19 [INFO] [stderr] Compiling toml v0.9.7 [INFO] [stderr] Compiling proptest-derive v0.3.0 [INFO] [stderr] Compiling ed25519 v1.5.3 [INFO] [stderr] Compiling bcs v0.1.6 [INFO] [stderr] Compiling serde_cbor v0.11.2 [INFO] [stderr] Compiling csv v1.3.1 [INFO] [stderr] Compiling serde-name v0.1.2 [INFO] [stderr] Compiling ed25519-dalek-fiat v0.1.0 [INFO] [stderr] Compiling tinytemplate v1.2.1 [INFO] [stderr] Compiling diem-crypto v0.0.3 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:7:13 [INFO] [stdout] | [INFO] [stdout] 7 | #![cfg_attr(mirai, allow(incomplete_features), feature(const_generics))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:25:7 [INFO] [stdout] | [INFO] [stdout] 25 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:68:11 [INFO] [stdout] | [INFO] [stdout] 68 | #[cfg(all(mirai, not(debug_assertions)))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:79:7 [INFO] [stdout] | [INFO] [stdout] 79 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:81:11 [INFO] [stdout] | [INFO] [stdout] 81 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:387:9 [INFO] [stdout] | [INFO] [stdout] 387 | add_tag!(&public_key, ValidatedPublicKeyTag); // This key has gone through validity checks. [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` 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 `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `batch` [INFO] [stdout] --> src/ed25519.rs:450:11 [INFO] [stdout] | [INFO] [stdout] 450 | #[cfg(feature = "batch")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `assert-private-keys-not-cloneable`, `cloneable-private-keys`, `default`, `fiat`, `fuzzing`, `proptest`, `proptest-derive`, `u32`, and `u64` [INFO] [stdout] = help: consider adding `batch` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:421:9 [INFO] [stdout] | [INFO] [stdout] 421 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/ed25519.rs:421:23 [INFO] [stdout] | [INFO] [stdout] 421 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/ed25519.rs:433:9 [INFO] [stdout] | [INFO] [stdout] 433 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/ed25519.rs:433:23 [INFO] [stdout] | [INFO] [stdout] 433 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/hash.rs:209:9 [INFO] [stdout] | [INFO] [stdout] 209 | assume!(index < Self::LENGTH_IN_BITS); // 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/hash.rs:217:9 [INFO] [stdout] | [INFO] [stdout] 217 | assume!(index < Self::LENGTH * 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: 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/hash.rs:435:9 [INFO] [stdout] | [INFO] [stdout] 435 | 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/hash.rs:436:9 [INFO] [stdout] | [INFO] [stdout] 436 | assume!(self.hash_bytes.len() == HashValue::LENGTH); // 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/hash.rs:437:9 [INFO] [stdout] | [INFO] [stdout] 437 | 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/multi_ed25519.rs:45:7 [INFO] [stdout] | [INFO] [stdout] 45 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/multi_ed25519.rs:47:11 [INFO] [stdout] | [INFO] [stdout] 47 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/multi_ed25519.rs:311:13 [INFO] [stdout] | [INFO] [stdout] 311 | add_tag!(&public_key, ValidatedPublicKeyTag); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` 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 `add_tag` (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/multi_ed25519.rs:489:9 [INFO] [stdout] | [INFO] [stdout] 489 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/multi_ed25519.rs:489:23 [INFO] [stdout] | [INFO] [stdout] 489 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/multi_ed25519.rs:505:9 [INFO] [stdout] | [INFO] [stdout] 505 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/multi_ed25519.rs:505:23 [INFO] [stdout] | [INFO] [stdout] 505 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling criterion v0.3.6 [INFO] [stderr] Compiling trybuild v1.0.111 [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:7:13 [INFO] [stdout] | [INFO] [stdout] 7 | #![cfg_attr(mirai, allow(incomplete_features), feature(const_generics))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:25:7 [INFO] [stdout] | [INFO] [stdout] 25 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/lib.rs:68:11 [INFO] [stdout] | [INFO] [stdout] 68 | #[cfg(all(mirai, not(debug_assertions)))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:79:7 [INFO] [stdout] | [INFO] [stdout] 79 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:81:11 [INFO] [stdout] | [INFO] [stdout] 81 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:387:9 [INFO] [stdout] | [INFO] [stdout] 387 | add_tag!(&public_key, ValidatedPublicKeyTag); // This key has gone through validity checks. [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` 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 `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `batch` [INFO] [stdout] --> src/ed25519.rs:450:11 [INFO] [stdout] | [INFO] [stdout] 450 | #[cfg(feature = "batch")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `assert-private-keys-not-cloneable`, `cloneable-private-keys`, `default`, `fiat`, `fuzzing`, `proptest`, `proptest-derive`, `u32`, and `u64` [INFO] [stdout] = help: consider adding `batch` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/ed25519.rs:421:9 [INFO] [stdout] | [INFO] [stdout] 421 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/ed25519.rs:421:23 [INFO] [stdout] | [INFO] [stdout] 421 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/ed25519.rs:433:9 [INFO] [stdout] | [INFO] [stdout] 433 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/ed25519.rs:433:23 [INFO] [stdout] | [INFO] [stdout] 433 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/hash.rs:209:9 [INFO] [stdout] | [INFO] [stdout] 209 | assume!(index < Self::LENGTH_IN_BITS); // 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/hash.rs:217:9 [INFO] [stdout] | [INFO] [stdout] 217 | assume!(index < Self::LENGTH * 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: 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/hash.rs:435:9 [INFO] [stdout] | [INFO] [stdout] 435 | 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/hash.rs:436:9 [INFO] [stdout] | [INFO] [stdout] 436 | assume!(self.hash_bytes.len() == HashValue::LENGTH); // 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/hash.rs:437:9 [INFO] [stdout] | [INFO] [stdout] 437 | 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/multi_ed25519.rs:45:7 [INFO] [stdout] | [INFO] [stdout] 45 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/multi_ed25519.rs:47:11 [INFO] [stdout] | [INFO] [stdout] 47 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/multi_ed25519.rs:311:13 [INFO] [stdout] | [INFO] [stdout] 311 | add_tag!(&public_key, ValidatedPublicKeyTag); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` 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 `add_tag` (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/multi_ed25519.rs:489:9 [INFO] [stdout] | [INFO] [stdout] 489 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/multi_ed25519.rs:489:23 [INFO] [stdout] | [INFO] [stdout] 489 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (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/multi_ed25519.rs:505:9 [INFO] [stdout] | [INFO] [stdout] 505 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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/multi_ed25519.rs:505:23 [INFO] [stdout] | [INFO] [stdout] 505 | precondition!(has_tag!(public_key, ValidatedPublicKeyTag)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` 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 `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: the method `gen` exists for struct `ThreadRng`, but its trait bounds were not satisfied [INFO] [stdout] --> src/unit_tests/hash_test.rs:146:36 [INFO] [stdout] | [INFO] [stdout] 146 | *byte = rand::thread_rng().gen(); [INFO] [stdout] | ^^^ method cannot be called on `ThreadRng` due to unsatisfied trait bounds [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/rand-0.8.5/src/rngs/thread.rs:62:1 [INFO] [stdout] | [INFO] [stdout] 62 | pub struct ThreadRng { [INFO] [stdout] | -------------------- doesn't satisfy `_: RngCore` or `_: Rng` [INFO] [stdout] | [INFO] [stdout] = note: the following trait bounds were not satisfied: [INFO] [stdout] `ThreadRng: _IMPL_ARBITRARY_FOR_HashValue::_proptest::prelude::RngCore` [INFO] [stdout] which is required by `ThreadRng: _IMPL_ARBITRARY_FOR_HashValue::_proptest::prelude::Rng` [INFO] [stdout] = help: items from traits can only be used if the trait is in scope [INFO] [stdout] help: trait `Rng` which provides `gen` is implemented but not in scope; perhaps you want to import it [INFO] [stdout] | [INFO] [stdout] 4 + use rand::Rng; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `Signature` [INFO] [stdout] --> src/unit_tests/ed25519_test.rs:19:41 [INFO] [stdout] | [INFO] [stdout] 19 | use ed25519_dalek::ed25519::signature::{Signature as _, Verifier as _}; [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0599`. [INFO] [stdout] [INFO] [stderr] error: could not compile `diem-crypto` (lib test) due to 1 previous error; 24 warnings emitted [INFO] running `Command { std: "docker" "inspect" "d8f4ed4157f9349a6aadc0574dff35d59605e332363d36e9d049c78745efb847", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "d8f4ed4157f9349a6aadc0574dff35d59605e332363d36e9d049c78745efb847", kill_on_drop: false }` [INFO] [stdout] d8f4ed4157f9349a6aadc0574dff35d59605e332363d36e9d049c78745efb847