[INFO] cloning repository https://github.com/hiroki-chen/MIRAI-Research [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/hiroki-chen/MIRAI-Research" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fhiroki-chen%2FMIRAI-Research", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fhiroki-chen%2FMIRAI-Research'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 20ccbe31b6c42f7ae6fd27a32c53cdd4bdf57eb0 [INFO] testing hiroki-chen/MIRAI-Research against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fhiroki-chen%2FMIRAI-Research" "/workspace/builds/worker-4-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-4-tc1/source'... [INFO] [stderr] done. [INFO] removed /workspace/builds/worker-4-tc1/source/rust-toolchain [INFO] started tweaking git repo https://github.com/hiroki-chen/MIRAI-Research [INFO] finished tweaking git repo https://github.com/hiroki-chen/MIRAI-Research [INFO] tweaked toml for git repo https://github.com/hiroki-chen/MIRAI-Research written to /workspace/builds/worker-4-tc1/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/hiroki-chen/MIRAI-Research on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/hiroki-chen/MIRAI-Research already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` [INFO] [stderr] note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest [INFO] [stderr] note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest [INFO] [stderr] note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions [INFO] [stderr] Updating git repository `https://github.com/facebookexperimental/MIRAI.git` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 9babcbf6e19cb4aac2dd1445f09d8fe6d42b539cd7b4db3e024b141c56348d68 [INFO] running `Command { std: "docker" "start" "-a" "9babcbf6e19cb4aac2dd1445f09d8fe6d42b539cd7b4db3e024b141c56348d68", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "9babcbf6e19cb4aac2dd1445f09d8fe6d42b539cd7b4db3e024b141c56348d68", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "9babcbf6e19cb4aac2dd1445f09d8fe6d42b539cd7b4db3e024b141c56348d68", kill_on_drop: false }` [INFO] [stdout] 9babcbf6e19cb4aac2dd1445f09d8fe6d42b539cd7b4db3e024b141c56348d68 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "build" "--frozen" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 7791b5240b4be73534d9e211d9171c26a4539b1f37292cbb29bfe56a17d75741 [INFO] running `Command { std: "docker" "start" "-a" "7791b5240b4be73534d9e211d9171c26a4539b1f37292cbb29bfe56a17d75741", kill_on_drop: false }` [INFO] [stderr] warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` [INFO] [stderr] note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest [INFO] [stderr] note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest [INFO] [stderr] note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions [INFO] [stderr] Compiling mirai-annotations v1.12.0 (https://github.com/facebookexperimental/MIRAI.git?rev=5ca2f1e#5ca2f1eb) [INFO] [stderr] Compiling another_crate v0.1.0 (/opt/rustwide/workdir/another_crate) [INFO] [stderr] Compiling mirai_research v0.1.0 (/opt/rustwide/workdir/main_crate) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> main_crate/src/main.rs:17:5 [INFO] [stdout] | [INFO] [stdout] 17 | verify!(v1[0] == 0); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:23:5 [INFO] [stdout] | [INFO] [stdout] 23 | add_tag!(&vec, SecretTaint); [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] --> main_crate/src/main.rs:25:5 [INFO] [stdout] | [INFO] [stdout] 25 | verify!(has_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:25:13 [INFO] [stdout] | [INFO] [stdout] 25 | verify!(has_tag!(&vec, SecretTaint)); [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] --> main_crate/src/main.rs:27:5 [INFO] [stdout] | [INFO] [stdout] 27 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:27:13 [INFO] [stdout] | [INFO] [stdout] 27 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:34:5 [INFO] [stdout] | [INFO] [stdout] 34 | add_tag!(&vec, SecretTaint); [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] --> main_crate/src/main.rs:36:5 [INFO] [stdout] | [INFO] [stdout] 36 | verify!(has_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:36:13 [INFO] [stdout] | [INFO] [stdout] 36 | verify!(has_tag!(&vec, SecretTaint)); [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] --> main_crate/src/main.rs:38:5 [INFO] [stdout] | [INFO] [stdout] 38 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:38:13 [INFO] [stdout] | [INFO] [stdout] 38 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:45:5 [INFO] [stdout] | [INFO] [stdout] 45 | add_tag!(&vec[0], SecretTaint); [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] --> main_crate/src/main.rs:47:5 [INFO] [stdout] | [INFO] [stdout] 47 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:47:13 [INFO] [stdout] | [INFO] [stdout] 47 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:49:5 [INFO] [stdout] | [INFO] [stdout] 49 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:49:13 [INFO] [stdout] | [INFO] [stdout] 49 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | add_tag!(&vec[0], SecretTaint); [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] --> main_crate/src/main.rs:60:5 [INFO] [stdout] | [INFO] [stdout] 60 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:60:13 [INFO] [stdout] | [INFO] [stdout] 60 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:61:5 [INFO] [stdout] | [INFO] [stdout] 61 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:61:13 [INFO] [stdout] | [INFO] [stdout] 61 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:67:5 [INFO] [stdout] | [INFO] [stdout] 67 | add_tag!(&wrapper, SecretTaint); [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] --> main_crate/src/main.rs:70:5 [INFO] [stdout] | [INFO] [stdout] 70 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:70:13 [INFO] [stdout] | [INFO] [stdout] 70 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | add_tag!(&vec, SecretTaint); [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] --> main_crate/src/main.rs:79:5 [INFO] [stdout] | [INFO] [stdout] 79 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:79:13 [INFO] [stdout] | [INFO] [stdout] 79 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:87:5 [INFO] [stdout] | [INFO] [stdout] 87 | add_tag!(&vec, SecretTaint); [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] --> main_crate/src/main.rs:89:5 [INFO] [stdout] | [INFO] [stdout] 89 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:89:13 [INFO] [stdout] | [INFO] [stdout] 89 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:95:5 [INFO] [stdout] | [INFO] [stdout] 95 | add_tag!(&vec[0], SecretTaint); [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] --> main_crate/src/main.rs:97:5 [INFO] [stdout] | [INFO] [stdout] 97 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:97:13 [INFO] [stdout] | [INFO] [stdout] 97 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:103:5 [INFO] [stdout] | [INFO] [stdout] 103 | add_tag!(&vec[0], SecretTaint); [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] --> main_crate/src/main.rs:105:5 [INFO] [stdout] | [INFO] [stdout] 105 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:105:13 [INFO] [stdout] | [INFO] [stdout] 105 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:111:5 [INFO] [stdout] | [INFO] [stdout] 111 | add_tag!(&wrapper.content, SecretTaint); [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] --> main_crate/src/main.rs:112:5 [INFO] [stdout] | [INFO] [stdout] 112 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:112:13 [INFO] [stdout] | [INFO] [stdout] 112 | verify!(has_tag!(&wrapper, SecretTaint)); [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] --> main_crate/src/main.rs:118:5 [INFO] [stdout] | [INFO] [stdout] 118 | add_tag!(&wrapper, SecretTaint); [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] --> main_crate/src/main.rs:119:5 [INFO] [stdout] | [INFO] [stdout] 119 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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] --> main_crate/src/main.rs:125:5 [INFO] [stdout] | [INFO] [stdout] 125 | add_tag!(&wrapper, SecretTaint); [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] --> main_crate/src/main.rs:127:5 [INFO] [stdout] | [INFO] [stdout] 127 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:127:13 [INFO] [stdout] | [INFO] [stdout] 127 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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] --> main_crate/src/main.rs:135:5 [INFO] [stdout] | [INFO] [stdout] 135 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:135:13 [INFO] [stdout] | [INFO] [stdout] 135 | verify!(has_tag!(&wrapper, SecretTaint)); [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] --> main_crate/src/main.rs:142:5 [INFO] [stdout] | [INFO] [stdout] 142 | add_tag!(&tainted, SecretTaint); [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] --> main_crate/src/main.rs:144:5 [INFO] [stdout] | [INFO] [stdout] 144 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:144:13 [INFO] [stdout] | [INFO] [stdout] 144 | verify!(has_tag!(&wrapper, SecretTaint)); [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] --> main_crate/src/main.rs:146:5 [INFO] [stdout] | [INFO] [stdout] 146 | verify!(does_not_have_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:146:13 [INFO] [stdout] | [INFO] [stdout] 146 | verify!(does_not_have_tag!(&wrapper, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:152:5 [INFO] [stdout] | [INFO] [stdout] 152 | add_tag!(&vec_wrapper, SecretTaint); [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] --> main_crate/src/main.rs:153:5 [INFO] [stdout] | [INFO] [stdout] 153 | verify!(has_tag!(&vec_wrapper.inner, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:153:13 [INFO] [stdout] | [INFO] [stdout] 153 | verify!(has_tag!(&vec_wrapper.inner, SecretTaint)); [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] --> main_crate/src/main.rs:160:5 [INFO] [stdout] | [INFO] [stdout] 160 | add_tag!(&vec_wrapper, SecretTaint); [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] --> main_crate/src/main.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | verify!(has_tag!(&vec_wrapper.inner[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:161:13 [INFO] [stdout] | [INFO] [stdout] 161 | verify!(has_tag!(&vec_wrapper.inner[0], SecretTaint)); [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] --> main_crate/src/main.rs:165:5 [INFO] [stdout] | [INFO] [stdout] 165 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:165:19 [INFO] [stdout] | [INFO] [stdout] 165 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:172:5 [INFO] [stdout] | [INFO] [stdout] 172 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:172:19 [INFO] [stdout] | [INFO] [stdout] 172 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:180:5 [INFO] [stdout] | [INFO] [stdout] 180 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:180:19 [INFO] [stdout] | [INFO] [stdout] 180 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:187:5 [INFO] [stdout] | [INFO] [stdout] 187 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:187:19 [INFO] [stdout] | [INFO] [stdout] 187 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:194:5 [INFO] [stdout] | [INFO] [stdout] 194 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:194:19 [INFO] [stdout] | [INFO] [stdout] 194 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:200:5 [INFO] [stdout] | [INFO] [stdout] 200 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:200:19 [INFO] [stdout] | [INFO] [stdout] 200 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:203:5 [INFO] [stdout] | [INFO] [stdout] 203 | verify!(does_not_have_tag!(&sanitized, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:203:13 [INFO] [stdout] | [INFO] [stdout] 203 | verify!(does_not_have_tag!(&sanitized, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:208:5 [INFO] [stdout] | [INFO] [stdout] 208 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:208:19 [INFO] [stdout] | [INFO] [stdout] 208 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:209:5 [INFO] [stdout] | [INFO] [stdout] 209 | verify!(has_tag!(&input, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:209:13 [INFO] [stdout] | [INFO] [stdout] 209 | verify!(has_tag!(&input, SecretTaint)); [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 0.77s [INFO] running `Command { std: "docker" "inspect" "7791b5240b4be73534d9e211d9171c26a4539b1f37292cbb29bfe56a17d75741", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "7791b5240b4be73534d9e211d9171c26a4539b1f37292cbb29bfe56a17d75741", kill_on_drop: false }` [INFO] [stdout] 7791b5240b4be73534d9e211d9171c26a4539b1f37292cbb29bfe56a17d75741 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--no-run" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 300576a3d8a8f4dd139b01f686ea6584cc2370dbe8141bdba209f2686e9dc387 [INFO] running `Command { std: "docker" "start" "-a" "300576a3d8a8f4dd139b01f686ea6584cc2370dbe8141bdba209f2686e9dc387", kill_on_drop: false }` [INFO] [stderr] warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` [INFO] [stderr] note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest [INFO] [stderr] note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest [INFO] [stderr] note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions [INFO] [stderr] Compiling mirai_research v0.1.0 (/opt/rustwide/workdir/main_crate) [INFO] [stderr] Compiling another_crate v0.1.0 (/opt/rustwide/workdir/another_crate) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> main_crate/src/main.rs:17:5 [INFO] [stdout] | [INFO] [stdout] 17 | verify!(v1[0] == 0); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:23:5 [INFO] [stdout] | [INFO] [stdout] 23 | add_tag!(&vec, SecretTaint); [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] --> main_crate/src/main.rs:25:5 [INFO] [stdout] | [INFO] [stdout] 25 | verify!(has_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:25:13 [INFO] [stdout] | [INFO] [stdout] 25 | verify!(has_tag!(&vec, SecretTaint)); [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] --> main_crate/src/main.rs:27:5 [INFO] [stdout] | [INFO] [stdout] 27 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:27:13 [INFO] [stdout] | [INFO] [stdout] 27 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:34:5 [INFO] [stdout] | [INFO] [stdout] 34 | add_tag!(&vec, SecretTaint); [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] --> main_crate/src/main.rs:36:5 [INFO] [stdout] | [INFO] [stdout] 36 | verify!(has_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:36:13 [INFO] [stdout] | [INFO] [stdout] 36 | verify!(has_tag!(&vec, SecretTaint)); [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] --> main_crate/src/main.rs:38:5 [INFO] [stdout] | [INFO] [stdout] 38 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:38:13 [INFO] [stdout] | [INFO] [stdout] 38 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:45:5 [INFO] [stdout] | [INFO] [stdout] 45 | add_tag!(&vec[0], SecretTaint); [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] --> main_crate/src/main.rs:47:5 [INFO] [stdout] | [INFO] [stdout] 47 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:47:13 [INFO] [stdout] | [INFO] [stdout] 47 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:49:5 [INFO] [stdout] | [INFO] [stdout] 49 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:49:13 [INFO] [stdout] | [INFO] [stdout] 49 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | add_tag!(&vec[0], SecretTaint); [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] --> main_crate/src/main.rs:60:5 [INFO] [stdout] | [INFO] [stdout] 60 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:60:13 [INFO] [stdout] | [INFO] [stdout] 60 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:61:5 [INFO] [stdout] | [INFO] [stdout] 61 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:61:13 [INFO] [stdout] | [INFO] [stdout] 61 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:67:5 [INFO] [stdout] | [INFO] [stdout] 67 | add_tag!(&wrapper, SecretTaint); [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] --> main_crate/src/main.rs:70:5 [INFO] [stdout] | [INFO] [stdout] 70 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:70:13 [INFO] [stdout] | [INFO] [stdout] 70 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | add_tag!(&vec, SecretTaint); [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] --> main_crate/src/main.rs:79:5 [INFO] [stdout] | [INFO] [stdout] 79 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:79:13 [INFO] [stdout] | [INFO] [stdout] 79 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:87:5 [INFO] [stdout] | [INFO] [stdout] 87 | add_tag!(&vec, SecretTaint); [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] --> main_crate/src/main.rs:89:5 [INFO] [stdout] | [INFO] [stdout] 89 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:89:13 [INFO] [stdout] | [INFO] [stdout] 89 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:95:5 [INFO] [stdout] | [INFO] [stdout] 95 | add_tag!(&vec[0], SecretTaint); [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] --> main_crate/src/main.rs:97:5 [INFO] [stdout] | [INFO] [stdout] 97 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:97:13 [INFO] [stdout] | [INFO] [stdout] 97 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:103:5 [INFO] [stdout] | [INFO] [stdout] 103 | add_tag!(&vec[0], SecretTaint); [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] --> main_crate/src/main.rs:105:5 [INFO] [stdout] | [INFO] [stdout] 105 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:105:13 [INFO] [stdout] | [INFO] [stdout] 105 | verify!(has_tag!(&vec[0], SecretTaint)); [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] --> main_crate/src/main.rs:111:5 [INFO] [stdout] | [INFO] [stdout] 111 | add_tag!(&wrapper.content, SecretTaint); [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] --> main_crate/src/main.rs:112:5 [INFO] [stdout] | [INFO] [stdout] 112 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:112:13 [INFO] [stdout] | [INFO] [stdout] 112 | verify!(has_tag!(&wrapper, SecretTaint)); [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] --> main_crate/src/main.rs:118:5 [INFO] [stdout] | [INFO] [stdout] 118 | add_tag!(&wrapper, SecretTaint); [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] --> main_crate/src/main.rs:119:5 [INFO] [stdout] | [INFO] [stdout] 119 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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] --> main_crate/src/main.rs:125:5 [INFO] [stdout] | [INFO] [stdout] 125 | add_tag!(&wrapper, SecretTaint); [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] --> main_crate/src/main.rs:127:5 [INFO] [stdout] | [INFO] [stdout] 127 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:127:13 [INFO] [stdout] | [INFO] [stdout] 127 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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] --> main_crate/src/main.rs:135:5 [INFO] [stdout] | [INFO] [stdout] 135 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:135:13 [INFO] [stdout] | [INFO] [stdout] 135 | verify!(has_tag!(&wrapper, SecretTaint)); [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] --> main_crate/src/main.rs:142:5 [INFO] [stdout] | [INFO] [stdout] 142 | add_tag!(&tainted, SecretTaint); [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] --> main_crate/src/main.rs:144:5 [INFO] [stdout] | [INFO] [stdout] 144 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:144:13 [INFO] [stdout] | [INFO] [stdout] 144 | verify!(has_tag!(&wrapper, SecretTaint)); [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] --> main_crate/src/main.rs:146:5 [INFO] [stdout] | [INFO] [stdout] 146 | verify!(does_not_have_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:146:13 [INFO] [stdout] | [INFO] [stdout] 146 | verify!(does_not_have_tag!(&wrapper, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:152:5 [INFO] [stdout] | [INFO] [stdout] 152 | add_tag!(&vec_wrapper, SecretTaint); [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] --> main_crate/src/main.rs:153:5 [INFO] [stdout] | [INFO] [stdout] 153 | verify!(has_tag!(&vec_wrapper.inner, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:153:13 [INFO] [stdout] | [INFO] [stdout] 153 | verify!(has_tag!(&vec_wrapper.inner, SecretTaint)); [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] --> main_crate/src/main.rs:160:5 [INFO] [stdout] | [INFO] [stdout] 160 | add_tag!(&vec_wrapper, SecretTaint); [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] --> main_crate/src/main.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | verify!(has_tag!(&vec_wrapper.inner[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:161:13 [INFO] [stdout] | [INFO] [stdout] 161 | verify!(has_tag!(&vec_wrapper.inner[0], SecretTaint)); [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] --> main_crate/src/main.rs:165:5 [INFO] [stdout] | [INFO] [stdout] 165 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:165:19 [INFO] [stdout] | [INFO] [stdout] 165 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:172:5 [INFO] [stdout] | [INFO] [stdout] 172 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:172:19 [INFO] [stdout] | [INFO] [stdout] 172 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:180:5 [INFO] [stdout] | [INFO] [stdout] 180 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:180:19 [INFO] [stdout] | [INFO] [stdout] 180 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:187:5 [INFO] [stdout] | [INFO] [stdout] 187 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:187:19 [INFO] [stdout] | [INFO] [stdout] 187 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:194:5 [INFO] [stdout] | [INFO] [stdout] 194 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:194:19 [INFO] [stdout] | [INFO] [stdout] 194 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:200:5 [INFO] [stdout] | [INFO] [stdout] 200 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:200:19 [INFO] [stdout] | [INFO] [stdout] 200 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:203:5 [INFO] [stdout] | [INFO] [stdout] 203 | verify!(does_not_have_tag!(&sanitized, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:203:13 [INFO] [stdout] | [INFO] [stdout] 203 | verify!(does_not_have_tag!(&sanitized, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_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 `does_not_have_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] --> main_crate/src/main.rs:208:5 [INFO] [stdout] | [INFO] [stdout] 208 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:208:19 [INFO] [stdout] | [INFO] [stdout] 208 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:209:5 [INFO] [stdout] | [INFO] [stdout] 209 | verify!(has_tag!(&input, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` 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 `verify` (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] --> main_crate/src/main.rs:209:13 [INFO] [stdout] | [INFO] [stdout] 209 | verify!(has_tag!(&input, SecretTaint)); [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 `test` profile [unoptimized + debuginfo] target(s) in 1.02s [INFO] running `Command { std: "docker" "inspect" "300576a3d8a8f4dd139b01f686ea6584cc2370dbe8141bdba209f2686e9dc387", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "300576a3d8a8f4dd139b01f686ea6584cc2370dbe8141bdba209f2686e9dc387", kill_on_drop: false }` [INFO] [stdout] 300576a3d8a8f4dd139b01f686ea6584cc2370dbe8141bdba209f2686e9dc387 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] e85d7d3056194fe4334b41705fd1e37b5167433f204374abddcd906469f97cc1 [INFO] running `Command { std: "docker" "start" "-a" "e85d7d3056194fe4334b41705fd1e37b5167433f204374abddcd906469f97cc1", kill_on_drop: false }` [INFO] [stderr] warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` [INFO] [stderr] note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest [INFO] [stderr] note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest [INFO] [stderr] note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:17:5 [INFO] [stderr] | [INFO] [stderr] 17 | verify!(v1[0] == 0); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:23:5 [INFO] [stderr] | [INFO] [stderr] 23 | add_tag!(&vec, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:25:5 [INFO] [stderr] | [INFO] [stderr] 25 | verify!(has_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:25:13 [INFO] [stderr] | [INFO] [stderr] 25 | verify!(has_tag!(&vec, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:27:5 [INFO] [stderr] | [INFO] [stderr] 27 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:27:13 [INFO] [stderr] | [INFO] [stderr] 27 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `does_not_have_tag` 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 `does_not_have_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:34:5 [INFO] [stderr] | [INFO] [stderr] 34 | add_tag!(&vec, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:36:5 [INFO] [stderr] | [INFO] [stderr] 36 | verify!(has_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:36:13 [INFO] [stderr] | [INFO] [stderr] 36 | verify!(has_tag!(&vec, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:38:5 [INFO] [stderr] | [INFO] [stderr] 38 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:38:13 [INFO] [stderr] | [INFO] [stderr] 38 | verify!(does_not_have_tag!(&vec, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `does_not_have_tag` 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 `does_not_have_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:45:5 [INFO] [stderr] | [INFO] [stderr] 45 | add_tag!(&vec[0], SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:47:5 [INFO] [stderr] | [INFO] [stderr] 47 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:47:13 [INFO] [stderr] | [INFO] [stderr] 47 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:49:5 [INFO] [stderr] | [INFO] [stderr] 49 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:49:13 [INFO] [stderr] | [INFO] [stderr] 49 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `does_not_have_tag` 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 `does_not_have_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:57:5 [INFO] [stderr] | [INFO] [stderr] 57 | add_tag!(&vec[0], SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:60:5 [INFO] [stderr] | [INFO] [stderr] 60 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:60:13 [INFO] [stderr] | [INFO] [stderr] 60 | verify!(does_not_have_tag!(&vec[0], SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `does_not_have_tag` 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 `does_not_have_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:61:5 [INFO] [stderr] | [INFO] [stderr] 61 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:61:13 [INFO] [stderr] | [INFO] [stderr] 61 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:67:5 [INFO] [stderr] | [INFO] [stderr] 67 | add_tag!(&wrapper, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:70:5 [INFO] [stderr] | [INFO] [stderr] 70 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:70:13 [INFO] [stderr] | [INFO] [stderr] 70 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:78:5 [INFO] [stderr] | [INFO] [stderr] 78 | add_tag!(&vec, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:79:5 [INFO] [stderr] | [INFO] [stderr] 79 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:79:13 [INFO] [stderr] | [INFO] [stderr] 79 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:87:5 [INFO] [stderr] | [INFO] [stderr] 87 | add_tag!(&vec, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:89:5 [INFO] [stderr] | [INFO] [stderr] 89 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:89:13 [INFO] [stderr] | [INFO] [stderr] 89 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:95:5 [INFO] [stderr] | [INFO] [stderr] 95 | add_tag!(&vec[0], SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:97:5 [INFO] [stderr] | [INFO] [stderr] 97 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:97:13 [INFO] [stderr] | [INFO] [stderr] 97 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:103:5 [INFO] [stderr] | [INFO] [stderr] 103 | add_tag!(&vec[0], SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:105:5 [INFO] [stderr] | [INFO] [stderr] 105 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:105:13 [INFO] [stderr] | [INFO] [stderr] 105 | verify!(has_tag!(&vec[0], SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:111:5 [INFO] [stderr] | [INFO] [stderr] 111 | add_tag!(&wrapper.content, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:112:5 [INFO] [stderr] | [INFO] [stderr] 112 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:112:13 [INFO] [stderr] | [INFO] [stderr] 112 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:118:5 [INFO] [stderr] | [INFO] [stderr] 118 | add_tag!(&wrapper, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:119:5 [INFO] [stderr] | [INFO] [stderr] 119 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:119:13 [INFO] [stderr] | [INFO] [stderr] 119 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:125:5 [INFO] [stderr] | [INFO] [stderr] 125 | add_tag!(&wrapper, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:127:5 [INFO] [stderr] | [INFO] [stderr] 127 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:127:13 [INFO] [stderr] | [INFO] [stderr] 127 | verify!(has_tag!(&wrapper.content, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:135:5 [INFO] [stderr] | [INFO] [stderr] 135 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:135:13 [INFO] [stderr] | [INFO] [stderr] 135 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:142:5 [INFO] [stderr] | [INFO] [stderr] 142 | add_tag!(&tainted, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:144:5 [INFO] [stderr] | [INFO] [stderr] 144 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:144:13 [INFO] [stderr] | [INFO] [stderr] 144 | verify!(has_tag!(&wrapper, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:146:5 [INFO] [stderr] | [INFO] [stderr] 146 | verify!(does_not_have_tag!(&wrapper, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:146:13 [INFO] [stderr] | [INFO] [stderr] 146 | verify!(does_not_have_tag!(&wrapper, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `does_not_have_tag` 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 `does_not_have_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:152:5 [INFO] [stderr] | [INFO] [stderr] 152 | add_tag!(&vec_wrapper, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:153:5 [INFO] [stderr] | [INFO] [stderr] 153 | verify!(has_tag!(&vec_wrapper.inner, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:153:13 [INFO] [stderr] | [INFO] [stderr] 153 | verify!(has_tag!(&vec_wrapper.inner, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:160:5 [INFO] [stderr] | [INFO] [stderr] 160 | add_tag!(&vec_wrapper, SecretTaint); [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 `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:161:5 [INFO] [stderr] | [INFO] [stderr] 161 | verify!(has_tag!(&vec_wrapper.inner[0], SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:161:13 [INFO] [stderr] | [INFO] [stderr] 161 | verify!(has_tag!(&vec_wrapper.inner[0], SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:165:5 [INFO] [stderr] | [INFO] [stderr] 165 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:165:19 [INFO] [stderr] | [INFO] [stderr] 165 | precondition!(has_tag!(&input, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:172:5 [INFO] [stderr] | [INFO] [stderr] 172 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:172:19 [INFO] [stderr] | [INFO] [stderr] 172 | precondition!(has_tag!(&input, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:180:5 [INFO] [stderr] | [INFO] [stderr] 180 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:180:19 [INFO] [stderr] | [INFO] [stderr] 180 | precondition!(has_tag!(&input, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:187:5 [INFO] [stderr] | [INFO] [stderr] 187 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:187:19 [INFO] [stderr] | [INFO] [stderr] 187 | precondition!(has_tag!(&input, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:194:5 [INFO] [stderr] | [INFO] [stderr] 194 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:194:19 [INFO] [stderr] | [INFO] [stderr] 194 | precondition!(has_tag!(&input, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:200:5 [INFO] [stderr] | [INFO] [stderr] 200 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:200:19 [INFO] [stderr] | [INFO] [stderr] 200 | precondition!(has_tag!(&input, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:203:5 [INFO] [stderr] | [INFO] [stderr] 203 | verify!(does_not_have_tag!(&sanitized, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:203:13 [INFO] [stderr] | [INFO] [stderr] 203 | verify!(does_not_have_tag!(&sanitized, SecretTaint)); [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 `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `does_not_have_tag` 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 `does_not_have_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:208:5 [INFO] [stderr] | [INFO] [stderr] 208 | precondition!(has_tag!(&input, SecretTaint)); [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] --> main_crate/src/main.rs:208:19 [INFO] [stderr] | [INFO] [stderr] 208 | precondition!(has_tag!(&input, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:209:5 [INFO] [stderr] | [INFO] [stderr] 209 | verify!(has_tag!(&input, SecretTaint)); [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 `verify` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `verify` 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 `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `mirai` [INFO] [stderr] --> main_crate/src/main.rs:209:13 [INFO] [stderr] | [INFO] [stderr] 209 | verify!(has_tag!(&input, SecretTaint)); [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 `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `mirai_research` (bin "mirai_research" test) generated 76 warnings [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.03s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/another_crate-c66d33a39031356a) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests src/main.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/mirai_research-424f5e4130f02053) [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" "e85d7d3056194fe4334b41705fd1e37b5167433f204374abddcd906469f97cc1", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "e85d7d3056194fe4334b41705fd1e37b5167433f204374abddcd906469f97cc1", kill_on_drop: false }` [INFO] [stdout] e85d7d3056194fe4334b41705fd1e37b5167433f204374abddcd906469f97cc1