[INFO] fetching crate v_escape 0.18.0...
[INFO] building v_escape-0.18.0 against try#d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6 for pr-146237-1
[INFO] extracting crate v_escape 0.18.0 into /workspace/builds/worker-2-tc2/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-2-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate v_escape 0.18.0 on toolchain d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "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" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[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" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 1486c2573d12e20cb8fe36d495465c3acbfb008887687001e5035f6fc2daae70
[INFO] running `Command { std: "docker" "start" "-a" "1486c2573d12e20cb8fe36d495465c3acbfb008887687001e5035f6fc2daae70", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "1486c2573d12e20cb8fe36d495465c3acbfb008887687001e5035f6fc2daae70", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "1486c2573d12e20cb8fe36d495465c3acbfb008887687001e5035f6fc2daae70", kill_on_drop: false }`
[INFO] [stdout] 1486c2573d12e20cb8fe36d495465c3acbfb008887687001e5035f6fc2daae70
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] afb730e0d3656e438bd10ebecb5b29139893901873c5727af0a95f6f63d49898
[INFO] running `Command { std: "docker" "start" "-a" "afb730e0d3656e438bd10ebecb5b29139893901873c5727af0a95f6f63d49898", kill_on_drop: false }`
[INFO] [stderr]    Compiling v_escape v0.18.0 (/opt/rustwide/workdir)
[INFO] [stderr]    Compiling 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] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 3.62s
[INFO] running `Command { std: "docker" "inspect" "afb730e0d3656e438bd10ebecb5b29139893901873c5727af0a95f6f63d49898", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "afb730e0d3656e438bd10ebecb5b29139893901873c5727af0a95f6f63d49898", kill_on_drop: false }`
[INFO] [stdout] afb730e0d3656e438bd10ebecb5b29139893901873c5727af0a95f6f63d49898
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 84d8c4534794b1101623a305778a33d28315dcdc1627cecee23dede9d2fdf613
[INFO] running `Command { std: "docker" "start" "-a" "84d8c4534794b1101623a305778a33d28315dcdc1627cecee23dede9d2fdf613", kill_on_drop: false }`
[INFO] [stderr]    Compiling v_escape v0.18.0 (/opt/rustwide/workdir)
[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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 `test` profile [unoptimized + debuginfo] target(s) in 5.73s
[INFO] running `Command { std: "docker" "inspect" "84d8c4534794b1101623a305778a33d28315dcdc1627cecee23dede9d2fdf613", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "84d8c4534794b1101623a305778a33d28315dcdc1627cecee23dede9d2fdf613", kill_on_drop: false }`
[INFO] [stdout] 84d8c4534794b1101623a305778a33d28315dcdc1627cecee23dede9d2fdf613
