[INFO] fetching crate regex-cursor 0.1.4...
[INFO] testing regex-cursor-0.1.4 against nightly-2024-10-28+rustflags=-Zrandomize-layout for randomize-layout
[INFO] extracting crate regex-cursor 0.1.4 into /workspace/builds/worker-3-tc2/source
[INFO] validating manifest of crates.io crate regex-cursor 0.1.4 on toolchain nightly-2024-10-28
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-10-28" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate regex-cursor 0.1.4
[INFO] finished tweaking crates.io crate regex-cursor 0.1.4
[INFO] tweaked toml for crates.io crate regex-cursor 0.1.4 written to /workspace/builds/worker-3-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-10-28" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 67 packages to latest compatible versions
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-10-28" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-10-28" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 620939beed90d21d45cf4be1d56035c73be8f5719dccf8787f5e4a8517ad50af
[INFO] running `Command { std: "docker" "start" "-a" "620939beed90d21d45cf4be1d56035c73be8f5719dccf8787f5e4a8517ad50af", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "620939beed90d21d45cf4be1d56035c73be8f5719dccf8787f5e4a8517ad50af", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "620939beed90d21d45cf4be1d56035c73be8f5719dccf8787f5e4a8517ad50af", kill_on_drop: false }`
[INFO] [stdout] 620939beed90d21d45cf4be1d56035c73be8f5719dccf8787f5e4a8517ad50af
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Zrandomize-layout" "-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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-10-28" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] c2b09187f5e5796890a6639b88f6987f51e7547b2a6d71df8570365c0125fcde
[INFO] running `Command { std: "docker" "start" "-a" "c2b09187f5e5796890a6639b88f6987f51e7547b2a6d71df8570365c0125fcde", kill_on_drop: false }`
[INFO] [stderr]    Compiling memchr v2.7.4
[INFO] [stderr]    Compiling regex-syntax v0.8.5
[INFO] [stderr]    Compiling str_indices v0.4.4
[INFO] [stderr]    Compiling ropey v1.6.1
[INFO] [stderr]    Compiling aho-corasick v1.1.3
[INFO] [stderr]    Compiling regex-automata v0.4.8
[INFO] [stderr]    Compiling regex-cursor v0.1.4 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition value: `perf-literal-multisubstring`
[INFO] [stdout]   --> src/engines/meta/literal.rs:22:14
[INFO] [stdout]    |
[INFO] [stdout] 22 |     if !cfg!(feature = "perf-literal-multisubstring") {
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]    = help: consider adding `perf-literal-multisubstring` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]  --> src/engines/pikevm.rs:1:7
[INFO] [stdout]   |
[INFO] [stdout] 1 | #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]   = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:219:7
[INFO] [stdout]     |
[INFO] [stdout] 219 | #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 340 |     instrument!(|c| c.reset(&self.nfa));
[INFO] [stdout]     |     ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 483 |     instrument!(|c| c.eprint(&self.nfa));
[INFO] [stdout]     |     ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 |     instrument!(|c| c.record_state_set(&curr.set));
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 540 |     instrument!(|c| c.record_step(sid));
[INFO] [stdout]     |     ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |           #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 598 | /     instrument!(|c| {
[INFO] [stdout] 599 | |         c.record_closure(sid);
[INFO] [stdout] 600 | |         c.record_stack_push(sid);
[INFO] [stdout] 601 | |     });
[INFO] [stdout]     | |______- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 655 |         instrument!(|c| c.record_set_insert(sid));
[INFO] [stdout]     |         ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |           #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 685 | /                 instrument!(|c| {
[INFO] [stdout] 686 | |                     for &alt in &alternates[1..] {
[INFO] [stdout] 687 | |                         c.record_stack_push(alt);
[INFO] [stdout] 688 | |                     }
[INFO] [stdout] 689 | |                 });
[INFO] [stdout]     | |__________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 694 |                 instrument!(|c| c.record_stack_push(sid));
[INFO] [stdout]     |                 ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 703 |                     instrument!(|c| c.record_stack_push(sid));
[INFO] [stdout]     |                     ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `regex_automata::MatchKind`
[INFO] [stdout]  --> src/literal.rs:2:9
[INFO] [stdout]   |
[INFO] [stdout] 2 | pub use regex_automata::MatchKind;
[INFO] [stdout]   |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_imports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: struct `HalfMatchesIter` is never constructed
[INFO] [stdout]    --> src/util/iter.rs:651:12
[INFO] [stdout]     |
[INFO] [stdout] 651 | pub struct HalfMatchesIter<C: Cursor, F>(TryHalfMatchesIter<C, F>);
[INFO] [stdout]     |            ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `HalfMatchesIter` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis
[INFO] [stdout]     = note: `#[warn(dead_code)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.11s
[INFO] running `Command { std: "docker" "inspect" "c2b09187f5e5796890a6639b88f6987f51e7547b2a6d71df8570365c0125fcde", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c2b09187f5e5796890a6639b88f6987f51e7547b2a6d71df8570365c0125fcde", kill_on_drop: false }`
[INFO] [stdout] c2b09187f5e5796890a6639b88f6987f51e7547b2a6d71df8570365c0125fcde
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Zrandomize-layout" "-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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-10-28" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] ad1c0b200baa6d6557954eb71d946399f70e1e6e57acc3d5e3bf6567a6fb4d7a
[INFO] running `Command { std: "docker" "start" "-a" "ad1c0b200baa6d6557954eb71d946399f70e1e6e57acc3d5e3bf6567a6fb4d7a", kill_on_drop: false }`
[INFO] [stderr]    Compiling serde v1.0.214
[INFO] [stderr]    Compiling rustix v0.38.38
[INFO] [stderr]    Compiling byteorder v1.5.0
[INFO] [stderr]    Compiling libm v0.2.11
[INFO] [stderr]    Compiling linux-raw-sys v0.4.14
[INFO] [stderr]    Compiling bitflags v2.6.0
[INFO] [stderr]    Compiling equivalent v1.0.1
[INFO] [stderr]    Compiling hashbrown v0.15.0
[INFO] [stderr]    Compiling winnow v0.6.20
[INFO] [stderr]    Compiling anyhow v1.0.92
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]    Compiling once_cell v1.20.2
[INFO] [stderr]    Compiling fastrand v2.1.1
[INFO] [stderr]    Compiling syn v2.0.86
[INFO] [stderr]    Compiling getrandom v0.2.15
[INFO] [stderr]    Compiling wait-timeout v0.2.0
[INFO] [stderr]    Compiling quick-error v1.2.3
[INFO] [stderr]    Compiling bit-vec v0.6.3
[INFO] [stderr]    Compiling rand_core v0.6.4
[INFO] [stderr]    Compiling fnv v1.0.7
[INFO] [stderr]    Compiling unarray v0.1.4
[INFO] [stderr]    Compiling lazy_static v1.5.0
[INFO] [stdout] warning: unexpected `cfg` condition value: `perf-literal-multisubstring`
[INFO] [stdout]   --> src/engines/meta/literal.rs:22:14
[INFO] [stdout]    |
[INFO] [stdout] 22 |     if !cfg!(feature = "perf-literal-multisubstring") {
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]    = help: consider adding `perf-literal-multisubstring` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]  --> src/engines/pikevm.rs:1:7
[INFO] [stdout]   |
[INFO] [stdout] 1 | #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]   = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:219:7
[INFO] [stdout]     |
[INFO] [stdout] 219 | #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 340 |     instrument!(|c| c.reset(&self.nfa));
[INFO] [stdout]     |     ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 483 |     instrument!(|c| c.eprint(&self.nfa));
[INFO] [stdout]     |     ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 |     instrument!(|c| c.record_state_set(&curr.set));
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 540 |     instrument!(|c| c.record_step(sid));
[INFO] [stdout]     |     ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |           #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 598 | /     instrument!(|c| {
[INFO] [stdout] 599 | |         c.record_closure(sid);
[INFO] [stdout] 600 | |         c.record_stack_push(sid);
[INFO] [stdout] 601 | |     });
[INFO] [stdout]     | |______- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 655 |         instrument!(|c| c.record_set_insert(sid));
[INFO] [stdout]     |         ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |           #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 685 | /                 instrument!(|c| {
[INFO] [stdout] 686 | |                     for &alt in &alternates[1..] {
[INFO] [stdout] 687 | |                         c.record_stack_push(alt);
[INFO] [stdout] 688 | |                     }
[INFO] [stdout] 689 | |                 });
[INFO] [stdout]     | |__________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 694 |                 instrument!(|c| c.record_stack_push(sid));
[INFO] [stdout]     |                 ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 703 |                     instrument!(|c| c.record_stack_push(sid));
[INFO] [stdout]     |                     ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `regex_automata::MatchKind`
[INFO] [stdout]  --> src/literal.rs:2:9
[INFO] [stdout]   |
[INFO] [stdout] 2 | pub use regex_automata::MatchKind;
[INFO] [stdout]   |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_imports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: struct `HalfMatchesIter` is never constructed
[INFO] [stdout]    --> src/util/iter.rs:651:12
[INFO] [stdout]     |
[INFO] [stdout] 651 | pub struct HalfMatchesIter<C: Cursor, F>(TryHalfMatchesIter<C, F>);
[INFO] [stdout]     |            ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `HalfMatchesIter` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis
[INFO] [stdout]     = note: `#[warn(dead_code)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling bit-set v0.5.3
[INFO] [stderr]    Compiling rand_xorshift v0.3.0
[INFO] [stderr]    Compiling indexmap v2.6.0
[INFO] [stderr]    Compiling serde_derive v1.0.214
[INFO] [stderr]    Compiling zerocopy-derive v0.7.35
[INFO] [stderr]    Compiling tempfile v3.13.0
[INFO] [stderr]    Compiling rusty-fork v0.3.0
[INFO] [stderr]    Compiling zerocopy v0.7.35
[INFO] [stderr]    Compiling ppv-lite86 v0.2.20
[INFO] [stderr]    Compiling rand_chacha v0.3.1
[INFO] [stderr]    Compiling rand v0.8.5
[INFO] [stderr]    Compiling proptest v1.5.0
[INFO] [stderr]    Compiling toml_datetime v0.6.8
[INFO] [stderr]    Compiling serde_spanned v0.6.8
[INFO] [stderr]    Compiling bstr v1.10.0
[INFO] [stderr]    Compiling toml_edit v0.22.22
[INFO] [stderr]    Compiling toml v0.8.19
[INFO] [stderr]    Compiling regex-test v0.1.1
[INFO] [stderr]    Compiling regex-cursor v0.1.4 (/opt/rustwide/workdir)
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/anchored.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 20 |     load!("anchored");
[INFO] [stdout]    |     ----------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/bytes.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 21 |     load!("bytes");
[INFO] [stdout]    |     -------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/crazy.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 22 |     load!("crazy");
[INFO] [stdout]    |     -------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/crlf.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 23 |     load!("crlf");
[INFO] [stdout]    |     ------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/earliest.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 24 |     load!("earliest");
[INFO] [stdout]    |     ----------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/empty.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 25 |     load!("empty");
[INFO] [stdout]    |     -------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/expensive.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 26 |     load!("expensive");
[INFO] [stdout]    |     ------------------ in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/flags.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 27 |     load!("flags");
[INFO] [stdout]    |     -------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/iter.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 28 |     load!("iter");
[INFO] [stdout]    |     ------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/leftmost-all.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 29 |     load!("leftmost-all");
[INFO] [stdout]    |     --------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/line-terminator.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 30 |     load!("line-terminator");
[INFO] [stdout]    |     ------------------------ in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/misc.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 31 |     load!("misc");
[INFO] [stdout]    |     ------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/multiline.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 32 |     load!("multiline");
[INFO] [stdout]    |     ------------------ in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/no-unicode.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 33 |     load!("no-unicode");
[INFO] [stdout]    |     ------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/overlapping.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 34 |     load!("overlapping");
[INFO] [stdout]    |     -------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/regression.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 35 |     load!("regression");
[INFO] [stdout]    |     ------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/set.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 36 |     load!("set");
[INFO] [stdout]    |     ------------ in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/substring.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 37 |     load!("substring");
[INFO] [stdout]    |     ------------------ in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/unicode.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 38 |     load!("unicode");
[INFO] [stdout]    |     ---------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/utf8.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 39 |     load!("utf8");
[INFO] [stdout]    |     ------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/word-boundary.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 40 |     load!("word-boundary");
[INFO] [stdout]    |     ---------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/word-boundary-special.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 41 |     load!("word-boundary-special");
[INFO] [stdout]    |     ------------------------------ in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/fowler/basic.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 42 |     load!("fowler/basic");
[INFO] [stdout]    |     --------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/fowler/nullsubexpr.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 43 |     load!("fowler/nullsubexpr");
[INFO] [stdout]    |     --------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../../regex/testdata/fowler/repetition.toml`: No such file or directory (os error 2)
[INFO] [stdout]   --> src/tests.rs:15:33
[INFO] [stdout]    |
[INFO] [stdout] 15 |             const DATA: &[u8] = include_bytes!(concat!("../../regex/testdata/", $name, ".toml"));
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 44 |     load!("fowler/repetition");
[INFO] [stdout]    |     -------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `perf-literal-multisubstring`
[INFO] [stdout]   --> src/engines/meta/literal.rs:22:14
[INFO] [stdout]    |
[INFO] [stdout] 22 |     if !cfg!(feature = "perf-literal-multisubstring") {
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]    = help: consider adding `perf-literal-multisubstring` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]  --> src/engines/pikevm.rs:1:7
[INFO] [stdout]   |
[INFO] [stdout] 1 | #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]   = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:219:7
[INFO] [stdout]     |
[INFO] [stdout] 219 | #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 340 |     instrument!(|c| c.reset(&self.nfa));
[INFO] [stdout]     |     ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 483 |     instrument!(|c| c.eprint(&self.nfa));
[INFO] [stdout]     |     ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 |     instrument!(|c| c.record_state_set(&curr.set));
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 540 |     instrument!(|c| c.record_step(sid));
[INFO] [stdout]     |     ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |           #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 598 | /     instrument!(|c| {
[INFO] [stdout] 599 | |         c.record_closure(sid);
[INFO] [stdout] 600 | |         c.record_stack_push(sid);
[INFO] [stdout] 601 | |     });
[INFO] [stdout]     | |______- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 655 |         instrument!(|c| c.record_set_insert(sid));
[INFO] [stdout]     |         ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |           #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 685 | /                 instrument!(|c| {
[INFO] [stdout] 686 | |                     for &alt in &alternates[1..] {
[INFO] [stdout] 687 | |                         c.record_stack_push(alt);
[INFO] [stdout] 688 | |                     }
[INFO] [stdout] 689 | |                 });
[INFO] [stdout]     | |__________________- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 694 |                 instrument!(|c| c.record_stack_push(sid));
[INFO] [stdout]     |                 ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `internal-instrument-pikevm`
[INFO] [stdout]    --> src/engines/pikevm.rs:211:15
[INFO] [stdout]     |
[INFO] [stdout] 211 |         #[cfg(feature = "internal-instrument-pikevm")]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 703 |                     instrument!(|c| c.record_stack_push(sid));
[INFO] [stdout]     |                     ----------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`, `perf-inline`, and `ropey`
[INFO] [stdout]     = help: consider adding `internal-instrument-pikevm` as a feature in `Cargo.toml`
[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 `instrument` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `regex_automata::MatchKind`
[INFO] [stdout]  --> src/literal.rs:2:9
[INFO] [stdout]   |
[INFO] [stdout] 2 | pub use regex_automata::MatchKind;
[INFO] [stdout]   |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_imports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `regex-cursor` (lib test) due to 25 previous errors; 13 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "ad1c0b200baa6d6557954eb71d946399f70e1e6e57acc3d5e3bf6567a6fb4d7a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "ad1c0b200baa6d6557954eb71d946399f70e1e6e57acc3d5e3bf6567a6fb4d7a", kill_on_drop: false }`
[INFO] [stdout] ad1c0b200baa6d6557954eb71d946399f70e1e6e57acc3d5e3bf6567a6fb4d7a
