[INFO] fetching crate v_escape 0.18.0... [INFO] checking v_escape-0.18.0 against master#8c32e313cccf7df531e2d49ffb8227bb92304aee for pr-145608-1 [INFO] extracting crate v_escape 0.18.0 into /workspace/builds/worker-7-tc1/source [INFO] started tweaking crates.io crate v_escape 0.18.0 [INFO] finished tweaking crates.io crate v_escape 0.18.0 [INFO] tweaked toml for crates.io crate v_escape 0.18.0 written to /workspace/builds/worker-7-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate v_escape 0.18.0 on toolchain 8c32e313cccf7df531e2d49ffb8227bb92304aee [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 6 packages to latest compatible versions [INFO] [stderr] Adding buf-min v0.6.1 (available: v0.7.1) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded buf-min v0.6.1 [INFO] [stderr] Downloaded v_escape_derive v0.9.1 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 3d23d69bdd634909a7e0d1696b094db405f38252f7db4fda085902931a565fe5 [INFO] running `Command { std: "docker" "start" "-a" "3d23d69bdd634909a7e0d1696b094db405f38252f7db4fda085902931a565fe5", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "3d23d69bdd634909a7e0d1696b094db405f38252f7db4fda085902931a565fe5", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "3d23d69bdd634909a7e0d1696b094db405f38252f7db4fda085902931a565fe5", kill_on_drop: false }` [INFO] [stdout] 3d23d69bdd634909a7e0d1696b094db405f38252f7db4fda085902931a565fe5 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] ee02833c78625cb8de7cff111b9b892fbdfdae99ce42e5a4b1f61f323f5f5566 [INFO] running `Command { std: "docker" "start" "-a" "ee02833c78625cb8de7cff111b9b892fbdfdae99ce42e5a4b1f61f323f5f5566", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.101 [INFO] [stderr] Compiling v_escape v0.18.0 (/opt/rustwide/workdir) [INFO] [stderr] Checking buf-min v0.6.1 [INFO] [stderr] Compiling quote v1.0.40 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling v_escape_derive v0.9.1 [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:2:1 [INFO] [stdout] | [INFO] [stdout] 2 | v_escape::new!(MyEscape; 60->"foo"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:2:1 [INFO] [stdout] | [INFO] [stdout] 2 | v_escape::new!(MyEscape; 60->"foo"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:2:1 [INFO] [stdout] | [INFO] [stdout] 2 | v_escape::new!(MyEscape; 60->"foo"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:2:1 [INFO] [stdout] | [INFO] [stdout] 2 | v_escape::new!(MyEscape; 60->"foo"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:238:5 [INFO] [stdout] | [INFO] [stdout] 238 | v_escape::new!(MyE; 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:238:5 [INFO] [stdout] | [INFO] [stdout] 238 | v_escape::new!(MyE; 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:238:5 [INFO] [stdout] | [INFO] [stdout] 238 | v_escape::new!(MyE; 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:238:5 [INFO] [stdout] | [INFO] [stdout] 238 | v_escape::new!(MyE; 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:364:9 [INFO] [stdout] | [INFO] [stdout] 364 | / v_escape::new!( [INFO] [stdout] 365 | | MyE; [INFO] [stdout] 366 | | 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"; [INFO] [stdout] 367 | | avx = false [INFO] [stdout] 368 | | ); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:364:9 [INFO] [stdout] | [INFO] [stdout] 364 | / v_escape::new!( [INFO] [stdout] 365 | | MyE; [INFO] [stdout] 366 | | 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"; [INFO] [stdout] 367 | | avx = false [INFO] [stdout] 368 | | ); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_sse` [INFO] [stdout] --> tests/lib.rs:364:9 [INFO] [stdout] | [INFO] [stdout] 364 | / v_escape::new!( [INFO] [stdout] 365 | | MyE; [INFO] [stdout] 366 | | 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"; [INFO] [stdout] 367 | | avx = false [INFO] [stdout] 368 | | ); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_sse` [INFO] [stdout] --> tests/lib.rs:364:9 [INFO] [stdout] | [INFO] [stdout] 364 | / v_escape::new!( [INFO] [stdout] 365 | | MyE; [INFO] [stdout] 366 | | 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"; [INFO] [stdout] 367 | | avx = false [INFO] [stdout] 368 | | ); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:378:9 [INFO] [stdout] | [INFO] [stdout] 378 | / v_escape::new!( [INFO] [stdout] 379 | | MyE; [INFO] [stdout] 380 | | 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"; [INFO] [stdout] 381 | | avx = false [INFO] [stdout] 382 | | ); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:378:9 [INFO] [stdout] | [INFO] [stdout] 378 | / v_escape::new!( [INFO] [stdout] 379 | | MyE; [INFO] [stdout] 380 | | 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"; [INFO] [stdout] 381 | | avx = false [INFO] [stdout] 382 | | ); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_sse` [INFO] [stdout] --> tests/lib.rs:378:9 [INFO] [stdout] | [INFO] [stdout] 378 | / v_escape::new!( [INFO] [stdout] 379 | | MyE; [INFO] [stdout] 380 | | 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"; [INFO] [stdout] 381 | | avx = false [INFO] [stdout] 382 | | ); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_sse` [INFO] [stdout] --> tests/lib.rs:378:9 [INFO] [stdout] | [INFO] [stdout] 378 | / v_escape::new!( [INFO] [stdout] 379 | | MyE; [INFO] [stdout] 380 | | 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"; [INFO] [stdout] 381 | | avx = false [INFO] [stdout] 382 | | ); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:393:5 [INFO] [stdout] | [INFO] [stdout] 393 | v_escape::new!(MyE; 65->""); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:393:5 [INFO] [stdout] | [INFO] [stdout] 393 | v_escape::new!(MyE; 65->""); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:393:5 [INFO] [stdout] | [INFO] [stdout] 393 | v_escape::new!(MyE; 65->""); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:393:5 [INFO] [stdout] | [INFO] [stdout] 393 | v_escape::new!(MyE; 65->""); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:405:9 [INFO] [stdout] | [INFO] [stdout] 405 | / v_escape::new!( [INFO] [stdout] 406 | | MyE; [INFO] [stdout] 407 | | '0'->"zero", '1'->"one", '2'->"two", '3'->"three", '4'->"four", '5'->"five", [INFO] [stdout] 408 | | '6'->"six", '7'->"seven", '8'->"eight", '9'->"nine" [INFO] [stdout] 409 | | ); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:405:9 [INFO] [stdout] | [INFO] [stdout] 405 | / v_escape::new!( [INFO] [stdout] 406 | | MyE; [INFO] [stdout] 407 | | '0'->"zero", '1'->"one", '2'->"two", '3'->"three", '4'->"four", '5'->"five", [INFO] [stdout] 408 | | '6'->"six", '7'->"seven", '8'->"eight", '9'->"nine" [INFO] [stdout] 409 | | ); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:405:9 [INFO] [stdout] | [INFO] [stdout] 405 | / v_escape::new!( [INFO] [stdout] 406 | | MyE; [INFO] [stdout] 407 | | '0'->"zero", '1'->"one", '2'->"two", '3'->"three", '4'->"four", '5'->"five", [INFO] [stdout] 408 | | '6'->"six", '7'->"seven", '8'->"eight", '9'->"nine" [INFO] [stdout] 409 | | ); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:405:9 [INFO] [stdout] | [INFO] [stdout] 405 | / v_escape::new!( [INFO] [stdout] 406 | | MyE; [INFO] [stdout] 407 | | '0'->"zero", '1'->"one", '2'->"two", '3'->"three", '4'->"four", '5'->"five", [INFO] [stdout] 408 | | '6'->"six", '7'->"seven", '8'->"eight", '9'->"nine" [INFO] [stdout] 409 | | ); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:437:9 [INFO] [stdout] | [INFO] [stdout] 437 | v_escape::new!(MyE; 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:437:9 [INFO] [stdout] | [INFO] [stdout] 437 | v_escape::new!(MyE; 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:437:9 [INFO] [stdout] | [INFO] [stdout] 437 | v_escape::new!(MyE; 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:437:9 [INFO] [stdout] | [INFO] [stdout] 437 | v_escape::new!(MyE; 65->"a", 60->"b", 61->"c", 66->"d", 80->"e", 81->"f"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:448:9 [INFO] [stdout] | [INFO] [stdout] 448 | v_escape::new!(MyE; 60->"a", 61->"b", 65->"c", 80->"d", 81->"e"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:448:9 [INFO] [stdout] | [INFO] [stdout] 448 | v_escape::new!(MyE; 60->"a", 61->"b", 65->"c", 80->"d", 81->"e"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:448:9 [INFO] [stdout] | [INFO] [stdout] 448 | v_escape::new!(MyE; 60->"a", 61->"b", 65->"c", 80->"d", 81->"e"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:448:9 [INFO] [stdout] | [INFO] [stdout] 448 | v_escape::new!(MyE; 60->"a", 61->"b", 65->"c", 80->"d", 81->"e"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:459:9 [INFO] [stdout] | [INFO] [stdout] 459 | v_escape::new!(MyE; 60->"a", 65->"c", 80->"d", 62->"e"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:459:9 [INFO] [stdout] | [INFO] [stdout] 459 | v_escape::new!(MyE; 60->"a", 65->"c", 80->"d", 62->"e"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:459:9 [INFO] [stdout] | [INFO] [stdout] 459 | v_escape::new!(MyE; 60->"a", 65->"c", 80->"d", 62->"e"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:459:9 [INFO] [stdout] | [INFO] [stdout] 459 | v_escape::new!(MyE; 60->"a", 65->"c", 80->"d", 62->"e"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:470:9 [INFO] [stdout] | [INFO] [stdout] 470 | v_escape::new!(MyE; 60->"a", 80->"b", 65->"c"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:470:9 [INFO] [stdout] | [INFO] [stdout] 470 | v_escape::new!(MyE; 60->"a", 80->"b", 65->"c"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:470:9 [INFO] [stdout] | [INFO] [stdout] 470 | v_escape::new!(MyE; 60->"a", 80->"b", 65->"c"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:470:9 [INFO] [stdout] | [INFO] [stdout] 470 | v_escape::new!(MyE; 60->"a", 80->"b", 65->"c"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:481:9 [INFO] [stdout] | [INFO] [stdout] 481 | v_escape::new!(MyE; 60->"a", 61->"b", 81->"c", 80->"d", 62->"e"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:481:9 [INFO] [stdout] | [INFO] [stdout] 481 | v_escape::new!(MyE; 60->"a", 61->"b", 81->"c", 80->"d", 62->"e"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:481:9 [INFO] [stdout] | [INFO] [stdout] 481 | v_escape::new!(MyE; 60->"a", 61->"b", 81->"c", 80->"d", 62->"e"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:481:9 [INFO] [stdout] | [INFO] [stdout] 481 | v_escape::new!(MyE; 60->"a", 61->"b", 81->"c", 80->"d", 62->"e"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:492:9 [INFO] [stdout] | [INFO] [stdout] 492 | v_escape::new!(MyE; 60->"a", 61->"b", 80->"c", 62->"d"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:492:9 [INFO] [stdout] | [INFO] [stdout] 492 | v_escape::new!(MyE; 60->"a", 61->"b", 80->"c", 62->"d"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:492:9 [INFO] [stdout] | [INFO] [stdout] 492 | v_escape::new!(MyE; 60->"a", 61->"b", 80->"c", 62->"d"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:492:9 [INFO] [stdout] | [INFO] [stdout] 492 | v_escape::new!(MyE; 60->"a", 61->"b", 80->"c", 62->"d"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:503:9 [INFO] [stdout] | [INFO] [stdout] 503 | v_escape::new!(MyE; 60->"a", 80->"b"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:503:9 [INFO] [stdout] | [INFO] [stdout] 503 | v_escape::new!(MyE; 60->"a", 80->"b"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:503:9 [INFO] [stdout] | [INFO] [stdout] 503 | v_escape::new!(MyE; 60->"a", 80->"b"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:503:9 [INFO] [stdout] | [INFO] [stdout] 503 | v_escape::new!(MyE; 60->"a", 80->"b"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:514:9 [INFO] [stdout] | [INFO] [stdout] 514 | v_escape::new!(MyE; 60->"a", 61->"b"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:514:9 [INFO] [stdout] | [INFO] [stdout] 514 | v_escape::new!(MyE; 60->"a", 61->"b"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:514:9 [INFO] [stdout] | [INFO] [stdout] 514 | v_escape::new!(MyE; 60->"a", 61->"b"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:514:9 [INFO] [stdout] | [INFO] [stdout] 514 | v_escape::new!(MyE; 60->"a", 61->"b"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:525:9 [INFO] [stdout] | [INFO] [stdout] 525 | v_escape::new!(MyE; 60->"f"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:525:9 [INFO] [stdout] | [INFO] [stdout] 525 | v_escape::new!(MyE; 60->"f"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:525:9 [INFO] [stdout] | [INFO] [stdout] 525 | v_escape::new!(MyE; 60->"f"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:525:9 [INFO] [stdout] | [INFO] [stdout] 525 | v_escape::new!(MyE; 60->"f"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:537:9 [INFO] [stdout] | [INFO] [stdout] 537 | v_escape::new!(MyE; ' ' -> "f"); [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 `$crate::derive` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::derive` may come from an old version of the `v_escape_derive` crate, try updating your dependency with `cargo update -p v_escape_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::derive` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `b_escape_nosimd` [INFO] [stdout] --> tests/lib.rs:537:9 [INFO] [stdout] | [INFO] [stdout] 537 | v_escape::new!(MyE; ' ' -> "f"); [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 `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `v_escape::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `v_escape::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:537:9 [INFO] [stdout] | [INFO] [stdout] 537 | v_escape::new!(MyE; ' ' -> "f"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `v_escape_avx` [INFO] [stdout] --> tests/lib.rs:537:9 [INFO] [stdout] | [INFO] [stdout] 537 | v_escape::new!(MyE; ' ' -> "f"); [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 `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::cfg_escape_bytes` may come from an old version of the `v_escape` crate, try updating your dependency with `cargo update -p v_escape` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::cfg_escape_bytes` which comes from the expansion of the macro `v_escape::new` (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 10.04s [INFO] running `Command { std: "docker" "inspect" "ee02833c78625cb8de7cff111b9b892fbdfdae99ce42e5a4b1f61f323f5f5566", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "ee02833c78625cb8de7cff111b9b892fbdfdae99ce42e5a4b1f61f323f5f5566", kill_on_drop: false }` [INFO] [stdout] ee02833c78625cb8de7cff111b9b892fbdfdae99ce42e5a4b1f61f323f5f5566