[INFO] fetching crate v_escape 0.18.0...
[INFO] testing v_escape-0.18.0 against master#0d162b25edd5bf0dba9a22e83b614f1113e90474 for pr-150681
[INFO] extracting crate v_escape 0.18.0 into /workspace/builds/worker-6-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-6-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate v_escape 0.18.0 on toolchain 0d162b25edd5bf0dba9a22e83b614f1113e90474
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "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" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "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]     Blocking waiting for file lock on package cache
[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" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded quote v1.0.43
[INFO] [stderr]   Downloaded buf-min v0.6.1
[INFO] [stderr]   Downloaded unicode-ident v1.0.22
[INFO] [stderr]   Downloaded proc-macro2 v1.0.105
[INFO] [stderr]   Downloaded v_escape_derive v0.9.1
[INFO] [stderr]   Downloaded syn v1.0.109
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 8a6e09452f992348ada70ce3d811f16fd6421eac9e1ffaad5dffd230d4050e5b
[INFO] running `Command { std: "docker" "start" "-a" "8a6e09452f992348ada70ce3d811f16fd6421eac9e1ffaad5dffd230d4050e5b", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "8a6e09452f992348ada70ce3d811f16fd6421eac9e1ffaad5dffd230d4050e5b", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "8a6e09452f992348ada70ce3d811f16fd6421eac9e1ffaad5dffd230d4050e5b", kill_on_drop: false }`
[INFO] [stdout] 8a6e09452f992348ada70ce3d811f16fd6421eac9e1ffaad5dffd230d4050e5b
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 1c5f22ba3844d1d69aaca668178e6ff4eb9f98659f7ac4aa78325b066499be5e
[INFO] running `Command { std: "docker" "start" "-a" "1c5f22ba3844d1d69aaca668178e6ff4eb9f98659f7ac4aa78325b066499be5e", kill_on_drop: false }`
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling v_escape v0.18.0 (/opt/rustwide/workdir)
[INFO] [stderr]    Compiling buf-min v0.6.1
[INFO] [stderr]    Compiling v_escape_derive v0.9.1
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 3.45s
[INFO] running `Command { std: "docker" "inspect" "1c5f22ba3844d1d69aaca668178e6ff4eb9f98659f7ac4aa78325b066499be5e", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "1c5f22ba3844d1d69aaca668178e6ff4eb9f98659f7ac4aa78325b066499be5e", kill_on_drop: false }`
[INFO] [stdout] 1c5f22ba3844d1d69aaca668178e6ff4eb9f98659f7ac4aa78325b066499be5e
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 4db5b74c5fede38723da61c191193a5273aca7f4bfd719c40d092c59a9b6520c
[INFO] running `Command { std: "docker" "start" "-a" "4db5b74c5fede38723da61c191193a5273aca7f4bfd719c40d092c59a9b6520c", 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 8.33s
[INFO] running `Command { std: "docker" "inspect" "4db5b74c5fede38723da61c191193a5273aca7f4bfd719c40d092c59a9b6520c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "4db5b74c5fede38723da61c191193a5273aca7f4bfd719c40d092c59a9b6520c", kill_on_drop: false }`
[INFO] [stdout] 4db5b74c5fede38723da61c191193a5273aca7f4bfd719c40d092c59a9b6520c
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] 542a9e5d1ed21b9de9d0bc6f3b89e5880b34621b0274bb390064613db085d9c1
[INFO] running `Command { std: "docker" "start" "-a" "542a9e5d1ed21b9de9d0bc6f3b89e5880b34621b0274bb390064613db085d9c1", kill_on_drop: false }`
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]  --> tests/lib.rs:2:1
[INFO] [stderr]   |
[INFO] [stderr] 2 | v_escape::new!(MyEscape; 60->"foo");
[INFO] [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = 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] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `$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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]  --> tests/lib.rs:2:1
[INFO] [stderr]   |
[INFO] [stderr] 2 | v_escape::new!(MyEscape; 60->"foo");
[INFO] [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = 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] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]  --> tests/lib.rs:2:1
[INFO] [stderr]   |
[INFO] [stderr] 2 | v_escape::new!(MyEscape; 60->"foo");
[INFO] [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = 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] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:238:5
[INFO] [stderr]     |
[INFO] [stderr] 238 |     v_escape::new!(MyE; 65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f");
[INFO] [stderr]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:238:5
[INFO] [stderr]     |
[INFO] [stderr] 238 |     v_escape::new!(MyE; 65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f");
[INFO] [stderr]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:238:5
[INFO] [stderr]     |
[INFO] [stderr] 238 |     v_escape::new!(MyE; 65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f");
[INFO] [stderr]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:364:9
[INFO] [stderr]     |
[INFO] [stderr] 364 | /         v_escape::new!(
[INFO] [stderr] 365 | |             MyE;
[INFO] [stderr] 366 | |             65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f";
[INFO] [stderr] 367 | |             avx = false
[INFO] [stderr] 368 | |         );
[INFO] [stderr]     | |_________^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:364:9
[INFO] [stderr]     |
[INFO] [stderr] 364 | /         v_escape::new!(
[INFO] [stderr] 365 | |             MyE;
[INFO] [stderr] 366 | |             65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f";
[INFO] [stderr] 367 | |             avx = false
[INFO] [stderr] 368 | |         );
[INFO] [stderr]     | |_________^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_sse`
[INFO] [stderr]    --> tests/lib.rs:364:9
[INFO] [stderr]     |
[INFO] [stderr] 364 | /         v_escape::new!(
[INFO] [stderr] 365 | |             MyE;
[INFO] [stderr] 366 | |             65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f";
[INFO] [stderr] 367 | |             avx = false
[INFO] [stderr] 368 | |         );
[INFO] [stderr]     | |_________^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:378:9
[INFO] [stderr]     |
[INFO] [stderr] 378 | /         v_escape::new!(
[INFO] [stderr] 379 | |             MyE;
[INFO] [stderr] 380 | |             65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f";
[INFO] [stderr] 381 | |             avx = false
[INFO] [stderr] 382 | |         );
[INFO] [stderr]     | |_________^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:378:9
[INFO] [stderr]     |
[INFO] [stderr] 378 | /         v_escape::new!(
[INFO] [stderr] 379 | |             MyE;
[INFO] [stderr] 380 | |             65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f";
[INFO] [stderr] 381 | |             avx = false
[INFO] [stderr] 382 | |         );
[INFO] [stderr]     | |_________^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_sse`
[INFO] [stderr]    --> tests/lib.rs:378:9
[INFO] [stderr]     |
[INFO] [stderr] 378 | /         v_escape::new!(
[INFO] [stderr] 379 | |             MyE;
[INFO] [stderr] 380 | |             65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f";
[INFO] [stderr] 381 | |             avx = false
[INFO] [stderr] 382 | |         );
[INFO] [stderr]     | |_________^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:393:5
[INFO] [stderr]     |
[INFO] [stderr] 393 |     v_escape::new!(MyE; 65->"");
[INFO] [stderr]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:393:5
[INFO] [stderr]     |
[INFO] [stderr] 393 |     v_escape::new!(MyE; 65->"");
[INFO] [stderr]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:393:5
[INFO] [stderr]     |
[INFO] [stderr] 393 |     v_escape::new!(MyE; 65->"");
[INFO] [stderr]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:405:9
[INFO] [stderr]     |
[INFO] [stderr] 405 | /         v_escape::new!(
[INFO] [stderr] 406 | |             MyE;
[INFO] [stderr] 407 | |             '0'->"zero",  '1'->"one",  '2'->"two",  '3'->"three",  '4'->"four",  '5'->"five",
[INFO] [stderr] 408 | |              '6'->"six",  '7'->"seven",  '8'->"eight",  '9'->"nine"
[INFO] [stderr] 409 | |         );
[INFO] [stderr]     | |_________^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:405:9
[INFO] [stderr]     |
[INFO] [stderr] 405 | /         v_escape::new!(
[INFO] [stderr] 406 | |             MyE;
[INFO] [stdout] 
[INFO] [stderr] 407 | |             '0'->"zero",  '1'->"one",  '2'->"two",  '3'->"three",  '4'->"four",  '5'->"five",
[INFO] [stdout] running 0 tests
[INFO] [stderr] 408 | |              '6'->"six",  '7'->"seven",  '8'->"eight",  '9'->"nine"
[INFO] [stdout] 
[INFO] [stderr] 409 | |         );
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stderr]     | |_________^
[INFO] [stdout] 
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:405:9
[INFO] [stderr]     |
[INFO] [stderr] 405 | /         v_escape::new!(
[INFO] [stderr] 406 | |             MyE;
[INFO] [stderr] 407 | |             '0'->"zero",  '1'->"one",  '2'->"two",  '3'->"three",  '4'->"four",  '5'->"five",
[INFO] [stderr] 408 | |              '6'->"six",  '7'->"seven",  '8'->"eight",  '9'->"nine"
[INFO] [stderr] 409 | |         );
[INFO] [stderr]     | |_________^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:437:9
[INFO] [stderr]     |
[INFO] [stderr] 437 |         v_escape::new!(MyE; 65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:437:9
[INFO] [stderr]     |
[INFO] [stderr] 437 |         v_escape::new!(MyE; 65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:437:9
[INFO] [stderr]     |
[INFO] [stderr] 437 |         v_escape::new!(MyE; 65->"a",  60->"b",  61->"c",  66->"d",  80->"e",  81->"f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:448:9
[INFO] [stderr]     |
[INFO] [stderr] 448 |         v_escape::new!(MyE; 60->"a",  61->"b",  65->"c",  80->"d",  81->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:448:9
[INFO] [stderr]     |
[INFO] [stderr] 448 |         v_escape::new!(MyE; 60->"a",  61->"b",  65->"c",  80->"d",  81->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:448:9
[INFO] [stderr]     |
[INFO] [stderr] 448 |         v_escape::new!(MyE; 60->"a",  61->"b",  65->"c",  80->"d",  81->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:459:9
[INFO] [stderr]     |
[INFO] [stderr] 459 |         v_escape::new!(MyE; 60->"a",  65->"c",  80->"d",  62->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:459:9
[INFO] [stderr]     |
[INFO] [stderr] 459 |         v_escape::new!(MyE; 60->"a",  65->"c",  80->"d",  62->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:459:9
[INFO] [stderr]     |
[INFO] [stderr] 459 |         v_escape::new!(MyE; 60->"a",  65->"c",  80->"d",  62->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:470:9
[INFO] [stderr]     |
[INFO] [stderr] 470 |         v_escape::new!(MyE; 60->"a",  80->"b",  65->"c");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:470:9
[INFO] [stderr]     |
[INFO] [stderr] 470 |         v_escape::new!(MyE; 60->"a",  80->"b",  65->"c");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:470:9
[INFO] [stderr]     |
[INFO] [stderr] 470 |         v_escape::new!(MyE; 60->"a",  80->"b",  65->"c");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:481:9
[INFO] [stderr]     |
[INFO] [stderr] 481 |         v_escape::new!(MyE; 60->"a",  61->"b",  81->"c",  80->"d",  62->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:481:9
[INFO] [stderr]     |
[INFO] [stderr] 481 |         v_escape::new!(MyE; 60->"a",  61->"b",  81->"c",  80->"d",  62->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:481:9
[INFO] [stderr]     |
[INFO] [stderr] 481 |         v_escape::new!(MyE; 60->"a",  61->"b",  81->"c",  80->"d",  62->"e");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:492:9
[INFO] [stderr]     |
[INFO] [stderr] 492 |         v_escape::new!(MyE; 60->"a",  61->"b",  80->"c",  62->"d");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:492:9
[INFO] [stderr]     |
[INFO] [stderr] 492 |         v_escape::new!(MyE; 60->"a",  61->"b",  80->"c",  62->"d");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:492:9
[INFO] [stderr]     |
[INFO] [stderr] 492 |         v_escape::new!(MyE; 60->"a",  61->"b",  80->"c",  62->"d");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:503:9
[INFO] [stderr]     |
[INFO] [stderr] 503 |         v_escape::new!(MyE; 60->"a",  80->"b");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:503:9
[INFO] [stderr]     |
[INFO] [stderr] 503 |         v_escape::new!(MyE; 60->"a",  80->"b");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:503:9
[INFO] [stderr]     |
[INFO] [stderr] 503 |         v_escape::new!(MyE; 60->"a",  80->"b");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:514:9
[INFO] [stderr]     |
[INFO] [stderr] 514 |         v_escape::new!(MyE; 60->"a",  61->"b");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:514:9
[INFO] [stderr]     |
[INFO] [stderr] 514 |         v_escape::new!(MyE; 60->"a",  61->"b");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:514:9
[INFO] [stderr]     |
[INFO] [stderr] 514 |         v_escape::new!(MyE; 60->"a",  61->"b");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:525:9
[INFO] [stderr]     |
[INFO] [stderr] 525 |         v_escape::new!(MyE; 60->"f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:525:9
[INFO] [stderr]     |
[INFO] [stderr] 525 |         v_escape::new!(MyE; 60->"f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:525:9
[INFO] [stderr]     |
[INFO] [stderr] 525 |         v_escape::new!(MyE; 60->"f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:537:9
[INFO] [stderr]     |
[INFO] [stderr] 537 |         v_escape::new!(MyE; ' ' -> "f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::derive` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `b_escape_nosimd`
[INFO] [stderr]    --> tests/lib.rs:537:9
[INFO] [stderr]     |
[INFO] [stderr] 537 |         v_escape::new!(MyE; ' ' -> "f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `v_escape::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `v_escape_avx`
[INFO] [stderr]    --> tests/lib.rs:537:9
[INFO] [stderr]     |
[INFO] [stderr] 537 |         v_escape::new!(MyE; ' ' -> "f");
[INFO] [stderr]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]     = help: try referring to `$crate::cfg_escape_bytes` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = 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] [stderr] 
[INFO] [stderr] warning: `v_escape` (test "lib") generated 64 warnings (16 duplicates)
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.05s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/v_escape-23135ed445264ad9)
[INFO] [stderr]      Running tests/lib.rs (/opt/rustwide/target/debug/deps/lib-27555bf89477a4fe)
[INFO] [stdout] 
[INFO] [stdout] running 20 tests
[INFO] [stdout] test bytes_buff::test_escape ... ok
[INFO] [stdout] test bytes_buff_nosimd::test_escape ... ok
[INFO] [stdout] test char_syntax::a::test_escape ... ok
[INFO] [stdout] test empty::test_escape ... ok
[INFO] [stdout] test test_avx::b::test_escape ... ok
[INFO] [stdout] test no_simd::a::test_escape ... ok
[INFO] [stdout] test no_avx::b::test_escape ... ok
[INFO] [stdout] test no_avx::a::test_escape ... ok
[INFO] [stdout] test test_avx::a::test_escape ... ok
[INFO] [stdout] test no_simd::b::test_escape ... ok
[INFO] [stdout] test test_avx::d::test_escape ... ok
[INFO] [stdout] test test_avx::e::test_escape ... ok
[INFO] [stdout] test test_avx::f::test_escape ... ok
[INFO] [stdout] test test_avx::i::test_escape ... ok
[INFO] [stdout] test test_avx::g::test_escape ... ok
[INFO] [stdout] test test_avx::c::test_escape ... ok
[INFO] [stdout] test test_avx::numbers::test_escape_a ... ok
[INFO] [stdout] test test_avx::h::test_escape ... ok
[INFO] [stdout] test test_escape ... ok
[INFO] [stdout] test test_avx::numbers::test_escape_b ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 20 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 13.92s
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests v_escape
[INFO] [stderr] error: couldn't read `src/../../README.md`: No such file or directory (os error 2)
[INFO] [stderr]    --> src/lib.rs:441:24
[INFO] [stderr]     |
[INFO] [stderr] 441 |     external_doc_test!(include_str!("../../README.md"));
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] 
[INFO] [stderr] error: attribute value must be a literal
[INFO] [stderr]    --> src/lib.rs:441:24
[INFO] [stderr]     |
[INFO] [stderr] 441 |     external_doc_test!(include_str!("../../README.md"));
[INFO] [stderr]     |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 2 previous errors
[INFO] [stderr] 
[INFO] [stderr] error: doctest failed, to rerun pass `--doc`
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   process didn't exit successfully: `/opt/rustwide/rustup-home/toolchains/0d162b25edd5bf0dba9a22e83b614f1113e90474/bin/rustdoc --edition=2018 --crate-type lib --color auto --crate-name v_escape --test src/lib.rs --test-run-directory /opt/rustwide/workdir --extern buf_min=/opt/rustwide/target/debug/deps/libbuf_min-3cf407771afd53f5.rlib --extern v_escape=/opt/rustwide/target/debug/deps/libv_escape-a4e067a5df7f229e.rlib --extern v_escape_derive=/opt/rustwide/target/debug/deps/libv_escape_derive-c54633e899d20922.so -L dependency=/opt/rustwide/target/debug/deps -C embed-bitcode=no --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' --cfg v_escape_sse --cfg v_escape_avx --cap-lints=forbid --error-format human` (exit status: 1)
[INFO] [stderr] note: test exited abnormally; to see the full output pass --no-capture to the harness.
[INFO] running `Command { std: "docker" "inspect" "542a9e5d1ed21b9de9d0bc6f3b89e5880b34621b0274bb390064613db085d9c1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "542a9e5d1ed21b9de9d0bc6f3b89e5880b34621b0274bb390064613db085d9c1", kill_on_drop: false }`
[INFO] [stdout] 542a9e5d1ed21b9de9d0bc6f3b89e5880b34621b0274bb390064613db085d9c1
