[INFO] cloning repository https://github.com/Siddid-Soni/advent-of-code-2024
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/Siddid-Soni/advent-of-code-2024" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] 915fb2b13fc06d331299d1921f625c39b6f55a58
[INFO] testing Siddid-Soni/advent-of-code-2024 against nightly-2025-01-18+rustflags=-Zrandomize-layout for randomize-layout-2
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024" "/workspace/builds/worker-1-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc2/source'...
[INFO] [stderr] done.
[INFO] validating manifest of git repo https://github.com/Siddid-Soni/advent-of-code-2024 on toolchain nightly-2025-01-18
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2025-01-18" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking git repo https://github.com/Siddid-Soni/advent-of-code-2024
[INFO] finished tweaking git repo https://github.com/Siddid-Soni/advent-of-code-2024
[INFO] tweaked toml for git repo https://github.com/Siddid-Soni/advent-of-code-2024 written to /workspace/builds/worker-1-tc2/source/Cargo.toml
[INFO] crate git repo https://github.com/Siddid-Soni/advent-of-code-2024 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2025-01-18" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2025-01-18" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] c30419bbd78d2b38d7f553a82a76208417fcaa535d3d75e764d1a9d5b45976d4
[INFO] running `Command { std: "docker" "start" "-a" "c30419bbd78d2b38d7f553a82a76208417fcaa535d3d75e764d1a9d5b45976d4", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "c30419bbd78d2b38d7f553a82a76208417fcaa535d3d75e764d1a9d5b45976d4", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c30419bbd78d2b38d7f553a82a76208417fcaa535d3d75e764d1a9d5b45976d4", kill_on_drop: false }`
[INFO] [stdout] c30419bbd78d2b38d7f553a82a76208417fcaa535d3d75e764d1a9d5b45976d4
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2025-01-18" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 0b381912dbe435b8b32c6f744338b128c03e4a4a33755c0374ad0a4b4692766d
[INFO] running `Command { std: "docker" "start" "-a" "0b381912dbe435b8b32c6f744338b128c03e4a4a33755c0374ad0a4b4692766d", kill_on_drop: false }`
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)` has the same output filename as the bin target `part1` in package `day-01 v0.1.0 (/opt/rustwide/workdir/day-01)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)` has the same output filename as the bin target `part1` in package `day-01 v0.1.0 (/opt/rustwide/workdir/day-01)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)` has the same output filename as the bin target `part2` in package `day-01 v0.1.0 (/opt/rustwide/workdir/day-01)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)` has the same output filename as the bin target `part2` in package `day-01 v0.1.0 (/opt/rustwide/workdir/day-01)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)` has the same output filename as the bin target `part1` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)` has the same output filename as the bin target `part1` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)` has the same output filename as the bin target `part2` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)` has the same output filename as the bin target `part2` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)` has the same output filename as the bin target `part1` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)` has the same output filename as the bin target `part1` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)` has the same output filename as the bin target `part2` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)` has the same output filename as the bin target `part2` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)` has the same output filename as the bin target `part1` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)` has the same output filename as the bin target `part1` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)` has the same output filename as the bin target `part2` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)` has the same output filename as the bin target `part2` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)` has the same output filename as the bin target `part1` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)` has the same output filename as the bin target `part1` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)` has the same output filename as the bin target `part2` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)` has the same output filename as the bin target `part2` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)` has the same output filename as the bin target `part1` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)` has the same output filename as the bin target `part1` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)` has the same output filename as the bin target `part2` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)` has the same output filename as the bin target `part2` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)` has the same output filename as the bin target `part1` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)` has the same output filename as the bin target `part1` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)` has the same output filename as the bin target `part2` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)` has the same output filename as the bin target `part2` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)` has the same output filename as the bin target `part1` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)` has the same output filename as the bin target `part1` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)` has the same output filename as the bin target `part2` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)` has the same output filename as the bin target `part2` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)` has the same output filename as the bin target `part1` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)` has the same output filename as the bin target `part1` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)` has the same output filename as the bin target `part2` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)` has the same output filename as the bin target `part2` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)` has the same output filename as the bin target `part1` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)` has the same output filename as the bin target `part1` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)` has the same output filename as the bin target `part2` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)` has the same output filename as the bin target `part2` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)` has the same output filename as the bin target `part1` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)` has the same output filename as the bin target `part1` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)` has the same output filename as the bin target `part2` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)` has the same output filename as the bin target `part2` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)` has the same output filename as the bin target `part1` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)` has the same output filename as the bin target `part1` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)` has the same output filename as the bin target `part2` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)` has the same output filename as the bin target `part2` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)` has the same output filename as the bin target `part1` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)` has the same output filename as the bin target `part1` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)` has the same output filename as the bin target `part2` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)` has the same output filename as the bin target `part2` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-15 v0.1.0 (/opt/rustwide/workdir/day-15)` has the same output filename as the bin target `part1` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-15 v0.1.0 (/opt/rustwide/workdir/day-15)` has the same output filename as the bin target `part1` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-15 v0.1.0 (/opt/rustwide/workdir/day-15)` has the same output filename as the bin target `part2` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-15 v0.1.0 (/opt/rustwide/workdir/day-15)` has the same output filename as the bin target `part2` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)` has the same output filename as the bin target `part1` in package `day-15 v0.1.0 (/opt/rustwide/workdir/day-15)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)` has the same output filename as the bin target `part1` in package `day-15 v0.1.0 (/opt/rustwide/workdir/day-15)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)` has the same output filename as the bin target `part2` in package `day-15 v0.1.0 (/opt/rustwide/workdir/day-15)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)` has the same output filename as the bin target `part2` in package `day-15 v0.1.0 (/opt/rustwide/workdir/day-15)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)` has the same output filename as the bin target `part1` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)` has the same output filename as the bin target `part1` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)` has the same output filename as the bin target `part2` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)` has the same output filename as the bin target `part2` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)` has the same output filename as the bin target `part1` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)` has the same output filename as the bin target `part1` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)` has the same output filename as the bin target `part2` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)` has the same output filename as the bin target `part2` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)` has the same output filename as the bin target `part1` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)` has the same output filename as the bin target `part1` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)` has the same output filename as the bin target `part2` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)` has the same output filename as the bin target `part2` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-20 v0.1.0 (/opt/rustwide/workdir/day-20)` has the same output filename as the bin target `part1` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-20 v0.1.0 (/opt/rustwide/workdir/day-20)` has the same output filename as the bin target `part1` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-20 v0.1.0 (/opt/rustwide/workdir/day-20)` has the same output filename as the bin target `part2` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-20 v0.1.0 (/opt/rustwide/workdir/day-20)` has the same output filename as the bin target `part2` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-21 v0.1.0 (/opt/rustwide/workdir/day-21)` has the same output filename as the bin target `part1` in package `day-20 v0.1.0 (/opt/rustwide/workdir/day-20)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-21 v0.1.0 (/opt/rustwide/workdir/day-21)` has the same output filename as the bin target `part1` in package `day-20 v0.1.0 (/opt/rustwide/workdir/day-20)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-21 v0.1.0 (/opt/rustwide/workdir/day-21)` has the same output filename as the bin target `part2` in package `day-20 v0.1.0 (/opt/rustwide/workdir/day-20)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-21 v0.1.0 (/opt/rustwide/workdir/day-21)` has the same output filename as the bin target `part2` in package `day-20 v0.1.0 (/opt/rustwide/workdir/day-20)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-22 v0.1.0 (/opt/rustwide/workdir/day-22)` has the same output filename as the bin target `part1` in package `day-21 v0.1.0 (/opt/rustwide/workdir/day-21)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-22 v0.1.0 (/opt/rustwide/workdir/day-22)` has the same output filename as the bin target `part1` in package `day-21 v0.1.0 (/opt/rustwide/workdir/day-21)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-22 v0.1.0 (/opt/rustwide/workdir/day-22)` has the same output filename as the bin target `part2` in package `day-21 v0.1.0 (/opt/rustwide/workdir/day-21)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-22 v0.1.0 (/opt/rustwide/workdir/day-22)` has the same output filename as the bin target `part2` in package `day-21 v0.1.0 (/opt/rustwide/workdir/day-21)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-23 v0.1.0 (/opt/rustwide/workdir/day-23)` has the same output filename as the bin target `part1` in package `day-22 v0.1.0 (/opt/rustwide/workdir/day-22)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part1` in package `day-23 v0.1.0 (/opt/rustwide/workdir/day-23)` has the same output filename as the bin target `part1` in package `day-22 v0.1.0 (/opt/rustwide/workdir/day-22)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-23 v0.1.0 (/opt/rustwide/workdir/day-23)` has the same output filename as the bin target `part2` in package `day-22 v0.1.0 (/opt/rustwide/workdir/day-22)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr] warning: output filename collision.
[INFO] [stderr] The bin target `part2` in package `day-23 v0.1.0 (/opt/rustwide/workdir/day-23)` has the same output filename as the bin target `part2` in package `day-22 v0.1.0 (/opt/rustwide/workdir/day-22)`.
[INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr] The targets should have unique names.
[INFO] [stderr] Consider changing their names to be unique or compiling them separately.
[INFO] [stderr] This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
[INFO] [stderr]    Compiling proc-macro2 v1.0.92
[INFO] [stderr]    Compiling unicode-ident v1.0.14
[INFO] [stderr]    Compiling memchr v2.7.4
[INFO] [stderr]    Compiling regex-syntax v0.8.5
[INFO] [stderr]    Compiling ident_case v1.0.1
[INFO] [stderr]    Compiling fnv v1.0.7
[INFO] [stderr]    Compiling strsim v0.11.1
[INFO] [stderr]    Compiling thiserror v1.0.69
[INFO] [stderr]    Compiling once_cell v1.20.2
[INFO] [stderr]    Compiling allocator-api2 v0.2.21
[INFO] [stderr]    Compiling cached_proc_macro_types v0.1.1
[INFO] [stderr]    Compiling ahash v0.8.11
[INFO] [stderr]    Compiling hashbrown v0.14.5
[INFO] [stderr]    Compiling aho-corasick v1.1.3
[INFO] [stderr]    Compiling quote v1.0.37
[INFO] [stderr]    Compiling syn v2.0.90
[INFO] [stderr]    Compiling regex-automata v0.4.9
[INFO] [stderr]    Compiling darling_core v0.20.10
[INFO] [stderr]    Compiling code-timing-macros v0.0.5
[INFO] [stderr]    Compiling thiserror-impl v1.0.69
[INFO] [stderr]    Compiling regex v1.11.1
[INFO] [stderr]    Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08)
[INFO] [stderr]    Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06)
[INFO] [stderr]    Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02)
[INFO] [stderr]    Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10)
[INFO] [stderr]    Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04)
[INFO] [stderr]    Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05)
[INFO] [stderr]    Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19)
[INFO] [stderr]    Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18)
[INFO] [stderr]    Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09)
[INFO] [stderr]    Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17)
[INFO] [stderr]    Compiling day-15 v0.1.0 (/opt/rustwide/workdir/day-15)
[INFO] [stderr]    Compiling day-21 v0.1.0 (/opt/rustwide/workdir/day-21)
[INFO] [stderr]    Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07)
[INFO] [stderr]    Compiling day-22 v0.1.0 (/opt/rustwide/workdir/day-22)
[INFO] [stderr]    Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12)
[INFO] [stderr]    Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16)
[INFO] [stderr]    Compiling day-23 v0.1.0 (/opt/rustwide/workdir/day-23)
[INFO] [stderr]    Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01)
[INFO] [stderr]    Compiling day-20 v0.1.0 (/opt/rustwide/workdir/day-20)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-15/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-15/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-05/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-05/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-01/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-01/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-05/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-05/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-19/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-19/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-07/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-07/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-20/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-20/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-16/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-16/input1.txt").unwrap());
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-18/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-18/input1.txt", (70,70)));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-12/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03)
[INFO] [stderr]    Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13)
[INFO] [stderr]    Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-23/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-23/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-18/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-18/input1.txt", 1024, (70,70)));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-21/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-20/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-20/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-12/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-21/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-16/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-16/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-19/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-19/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-07/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-07/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-01/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-01/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-15/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-15/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-08/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-08/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-08/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-08/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-17/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process());
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-17/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process());
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-22/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-22/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-22/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-22/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-10/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-10/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-04/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-04/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-04/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-04/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-10/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-10/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-02/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-02/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-02/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-02/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-06/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-06/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-09/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-06/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-06/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-09/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling darling_macro v0.20.10
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-13/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-14/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-03/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-03/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-14/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-13/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-03/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-03/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling darling v0.20.10
[INFO] [stderr]    Compiling cached_proc_macro v0.23.0
[INFO] [stderr]    Compiling cached v0.54.0
[INFO] [stderr]    Compiling day-11 v0.1.0 (/opt/rustwide/workdir/day-11)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-11/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-11/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 18.07s
[INFO] running `Command { std: "docker" "inspect" "0b381912dbe435b8b32c6f744338b128c03e4a4a33755c0374ad0a4b4692766d", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "0b381912dbe435b8b32c6f744338b128c03e4a4a33755c0374ad0a4b4692766d", kill_on_drop: false }`
[INFO] [stdout] 0b381912dbe435b8b32c6f744338b128c03e4a4a33755c0374ad0a4b4692766d
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2025-01-18" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 86ca467142fd4627d2d690368bc3b7849a025489739729f0062c4f982425197b
[INFO] running `Command { std: "docker" "start" "-a" "86ca467142fd4627d2d690368bc3b7849a025489739729f0062c4f982425197b", kill_on_drop: false }`
[INFO] [stderr]    Compiling rustix v0.38.41
[INFO] [stderr]    Compiling bitflags v2.6.0
[INFO] [stderr]    Compiling linux-raw-sys v0.4.14
[INFO] [stderr]    Compiling anstyle v1.0.10
[INFO] [stderr]    Compiling clap_lex v0.7.4
[INFO] [stderr]    Compiling libc v0.2.167
[INFO] [stderr]    Compiling condtype v1.3.0
[INFO] [stderr]    Compiling regex-lite v0.1.6
[INFO] [stderr]    Compiling divan-macros v0.1.17
[INFO] [stderr]    Compiling terminal_size v0.4.1
[INFO] [stderr]    Compiling clap_builder v4.5.23
[INFO] [stderr]    Compiling clap v4.5.23
[INFO] [stderr]    Compiling divan v0.1.17
[INFO] [stderr]    Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03)
[INFO] [stderr]    Compiling day-15 v0.1.0 (/opt/rustwide/workdir/day-15)
[INFO] [stderr]    Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12)
[INFO] [stderr]    Compiling day-20 v0.1.0 (/opt/rustwide/workdir/day-20)
[INFO] [stderr]    Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02)
[INFO] [stderr]    Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05)
[INFO] [stderr]    Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04)
[INFO] [stderr]    Compiling day-23 v0.1.0 (/opt/rustwide/workdir/day-23)
[INFO] [stderr]    Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07)
[INFO] [stderr]    Compiling day-22 v0.1.0 (/opt/rustwide/workdir/day-22)
[INFO] [stderr]    Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-04/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-04/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-03/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-03/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-05/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-05/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-15/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-15/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-23/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-07/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-07/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-20/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-20/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-12/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-02/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-02/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-03/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-03/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08)
[INFO] [stderr]    Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-08/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-08/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16)
[INFO] [stderr]    Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06)
[INFO] [stderr]    Compiling day-21 v0.1.0 (/opt/rustwide/workdir/day-21)
[INFO] [stderr]    Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-06/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-06/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-14/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-11 v0.1.0 (/opt/rustwide/workdir/day-11)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-22/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-22/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-11/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-07/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-07/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-13/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-09/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-13/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18)
[INFO] [stderr]    Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-22/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-22/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17)
[INFO] [stderr]    Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-01/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-01/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-11/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-19/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-19/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-17/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process());
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-02/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-02/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-14/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-18/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-18/input1.txt", (70,70)));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-16/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-16/input1.txt").unwrap());
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-12/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-10/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-10/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-09/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-20/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-20/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-21/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-06/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-06/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-08/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-08/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-01/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-01/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-18/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-18/input1.txt", 1024, (70,70)));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-04/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-04/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-16/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-16/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-19/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-19/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-17/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process());
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-21/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-10/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-10/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-15/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-15/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-23/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-05/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-05/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (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 12.51s
[INFO] running `Command { std: "docker" "inspect" "86ca467142fd4627d2d690368bc3b7849a025489739729f0062c4f982425197b", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "86ca467142fd4627d2d690368bc3b7849a025489739729f0062c4f982425197b", kill_on_drop: false }`
[INFO] [stdout] 86ca467142fd4627d2d690368bc3b7849a025489739729f0062c4f982425197b
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2025-01-18" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] a659c67fd99eb0f2beef4258f8e0b46ddff7686ae97f3984bd95a87db039eb26
[INFO] running `Command { std: "docker" "start" "-a" "a659c67fd99eb0f2beef4258f8e0b46ddff7686ae97f3984bd95a87db039eb26", kill_on_drop: false }`
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-02/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-02/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-06/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-06/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-19/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-19/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-16/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-16/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-22/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-22/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-14/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `day-02` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-06` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-19` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-16` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-22` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-14` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-07/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-07/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-08/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-08/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-13/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-15/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-15/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-05/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-05/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-15/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-15/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-17/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process());
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-21/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-08/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-08/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `day-07` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-08` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-13` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-15` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-05` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-15` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-17` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-21` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-08` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-19/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-19/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-02/src/bin/part2.rs:6:18
[INFO] [stderr]   |
[INFO] [stderr] 6 |     let result = time_snippet!(process("day-02/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-16/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-16/input1.txt").unwrap());
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-20/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-20/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-09/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-06/src/bin/part2.rs:6:18
[INFO] [stderr]   |
[INFO] [stderr] 6 |     let result = time_snippet!(process("day-06/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-14/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-18/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-18/input1.txt", 1024, (70,70)));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `day-19` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-02` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-16` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-20` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-09` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-06` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-14` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-18` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-11/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-11/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-07/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-07/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-13/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-01/src/bin/part2.rs:6:18
[INFO] [stderr]   |
[INFO] [stderr] 6 |     let result = time_snippet!(process("day-01/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-23/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `day-11` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-11` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-07` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-13` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-01` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-23` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-21/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-18/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-18/input1.txt", (70,70)));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-17/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process());
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-05/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-05/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout] 
[INFO] [stderr]  --> day-01/src/bin/part1.rs:5:18
[INFO] [stdout] running 2 tests
[INFO] [stderr]   |
[INFO] [stdout] test part1::tests::test_process ... ok
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-01/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-12/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-09/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-23/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-22/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-22/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-03/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-03/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `day-21` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-18` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-17` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-05` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-01` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-12` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-09` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-23` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-22` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-03` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-20/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-20/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-10/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-10/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-10/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-10/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-03/src/bin/part2.rs:6:18
[INFO] [stderr]   |
[INFO] [stderr] 6 |     let result = time_snippet!(process("day-03/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-12/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-04/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-04/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-04/src/bin/part2.rs:6:18
[INFO] [stderr]   |
[INFO] [stderr] 6 |     let result = time_snippet!(process("day-04/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[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 `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[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 `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `day-20` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-10` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-10` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-03` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-12` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-04` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-04` (bin "part2" test) generated 1 warning
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.18s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_01-4e0104119e0da9dc)
[INFO] [stderr]      Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/deps/part1-3d4106d1c9f03eb1)
[INFO] [stdout] test part2::tests::test_process ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/deps/part2-06deb415846b1bbe)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_02-d936d9f3e3d03515)
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test part1::tests::test_process ... ok
[INFO] [stdout] test part2::tests::test_process ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/deps/part1-d6e49c7c82f5b4ce)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/deps/part2-03676a6aec41391c)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_03-f0ae8cab987bc362)
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test part1::tests::test_process ... ok
[INFO] [stdout] test part2::tests::test_process ... FAILED
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout] 
[INFO] [stdout] ---- part2::tests::test_process stdout ----
[INFO] [stdout] 
[INFO] [stdout] thread 'part2::tests::test_process' panicked at day-03/src/part2.rs:32:9:
[INFO] [stdout] assertion `left == right` failed
[INFO] [stdout]   left: 42
[INFO] [stdout]  right: 48
[INFO] [stdout] stack backtrace:
[INFO] [stdout]    0:     0x649ba88862ba - std::backtrace_rs::backtrace::libunwind::trace::hb059275cfc8d6126
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
[INFO] [stdout]    1:     0x649ba88862ba - std::backtrace_rs::backtrace::trace_unsynchronized::h2da071e4327ce3ee
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
[INFO] [stdout]    2:     0x649ba88862ba - std::sys::backtrace::_print_fmt::h842a1474e6f8d23f
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:66:9
[INFO] [stdout]    3:     0x649ba88862ba - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h71a62eb3b9696b12
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:39:26
[INFO] [stdout]    4:     0x649ba88ae603 - core::fmt::rt::Argument::fmt::hdb6b616786b41dc1
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/fmt/rt.rs:177:76
[INFO] [stdout]    5:     0x649ba88ae603 - core::fmt::write::h2cc1698af7e2d686
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/fmt/mod.rs:1440:21
[INFO] [stdout]    6:     0x649ba8882e13 - std::io::Write::write_fmt::hab1b4cd059a79022
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/io/mod.rs:1887:15
[INFO] [stdout]    7:     0x649ba8886102 - std::sys::backtrace::BacktraceLock::print::h147fe35b4ea13b08
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:42:9
[INFO] [stdout]    8:     0x649ba88876df - std::panicking::default_hook::{{closure}}::hbd44223dbdc0d208
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:298:22
[INFO] [stdout]    9:     0x649ba88874f8 - std::panicking::default_hook::h20f81eb0576efcec
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:322:9
[INFO] [stdout]   10:     0x649ba85d3f53 - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::hdb53814c496a4d34
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/alloc/src/boxed.rs:2027:9
[INFO] [stdout]   11:     0x649ba85d3f53 - test::test_main::{{closure}}::hc0a4963c59427c24
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:134:21
[INFO] [stdout]   12:     0x649ba88881d3 - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::h591b2225413a77e9
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/alloc/src/boxed.rs:2027:9
[INFO] [stdout]   13:     0x649ba88881d3 - std::panicking::rust_panic_with_hook::h625eea43051b2edc
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:839:13
[INFO] [stdout]   14:     0x649ba8887e8a - std::panicking::begin_panic_handler::{{closure}}::h4f9159cfbc3f6bd3
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:704:13
[INFO] [stdout]   15:     0x649ba88867b9 - std::sys::backtrace::__rust_end_short_backtrace::h0390abce48353151
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:168:18
[INFO] [stdout]   16:     0x649ba8887b1d - rust_begin_unwind
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:695:5
[INFO] [stdout]   17:     0x649ba88acc90 - core::panicking::panic_fmt::h9e7c637e9e5f29c9
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/panicking.rs:75:14
[INFO] [stdout]   18:     0x649ba88ad082 - core::panicking::assert_failed_inner::h538bec7c1374cd9c
[INFO] [stdout]   19:     0x649ba886592c - core::panicking::assert_failed::hd02c0d569d89af5b
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/panicking.rs:364:5
[INFO] [stdout]   20:     0x649ba8599e49 - day_03::part2::tests::test_process::h77cfda7baeb9ccdf
[INFO] [stdout]                                at /opt/rustwide/workdir/day-03/src/part2.rs:32:9
[INFO] [stdout]   21:     0x649ba8599dc7 - day_03::part2::tests::test_process::{{closure}}::h19135a500ca1b957
[INFO] [stdout]                                at /opt/rustwide/workdir/day-03/src/part2.rs:31:22
[INFO] [stdout]   22:     0x649ba8594db6 - core::ops::function::FnOnce::call_once::h7efc3fb0122b2fd0
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   23:     0x649ba85d96ab - core::ops::function::FnOnce::call_once::he27718dfdd183f43
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   24:     0x649ba85d96ab - test::__rust_begin_short_backtrace::h4e84902998457a5d
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:632:18
[INFO] [stdout]   25:     0x649ba85d85e3 - test::run_test_in_process::{{closure}}::h7176fd18fc1feca0
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:655:60
[INFO] [stdout]   26:     0x649ba85d85e3 - <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::hf79cff2a624d8cf7
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/panic/unwind_safe.rs:272:9
[INFO] [stdout]   27:     0x649ba85d85e3 - std::panicking::try::do_call::h3da0561d9ab99c25
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:587:40
[INFO] [stdout]   28:     0x649ba85d85e3 - std::panicking::try::h41c9fa508bc61df6
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:550:19
[INFO] [stdout]   29:     0x649ba85d85e3 - std::panic::catch_unwind::h6b3ff07bb5afad93
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panic.rs:358:14
[INFO] [stdout]   30:     0x649ba85d85e3 - test::run_test_in_process::hc7253dd11b39b9f4
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:655:27
[INFO] [stdout]   31:     0x649ba85d85e3 - test::run_test::{{closure}}::hfb2007f8649c30bb
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:576:43
[INFO] [stdout]   32:     0x649ba859b6c5 - test::run_test::{{closure}}::h56a17aa7a282a9f4
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:606:41
[INFO] [stdout]   33:     0x649ba859b6c5 - std::sys::backtrace::__rust_begin_short_backtrace::hd2d2d2fb8e8c6aac
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:152:18
[INFO] [stdout]   34:     0x649ba859efaa - std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::h4faa3f9db6133423
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/thread/mod.rs:559:17
[INFO] [stdout]   35:     0x649ba859efaa - <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::hf2e855a36a4ea846
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/panic/unwind_safe.rs:272:9
[INFO] [stdout]   36:     0x649ba859efaa - std::panicking::try::do_call::h2f73af3616c35465
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:587:40
[INFO] [stdout]   37:     0x649ba859efaa - std::panicking::try::hd1660ce9efadef5a
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:550:19
[INFO] [stdout]   38:     0x649ba859efaa - std::panic::catch_unwind::h5ee8d7823b8ca744
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panic.rs:358:14
[INFO] [stdout]   39:     0x649ba859efaa - std::thread::Builder::spawn_unchecked_::{{closure}}::h53c3a1894dce8407
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/thread/mod.rs:557:30
[INFO] [stdout]   40:     0x649ba859efaa - core::ops::function::FnOnce::call_once{{vtable.shim}}::h048ce291ad4f62bf
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   41:     0x649ba888c10b - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::ha52bedf99a3b4981
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/alloc/src/boxed.rs:2013:9
[INFO] [stdout]   42:     0x649ba888c10b - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h567748934d80ccf8
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/alloc/src/boxed.rs:2013:9
[INFO] [stdout]   43:     0x649ba888c10b - std::sys::pal::unix::thread::Thread::new::thread_start::h2d970728ae887adc
[INFO] [stdout]                                at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/pal/unix/thread.rs:106:17
[INFO] [stdout]   44:     0x70425c1c3ac3 - <unknown>
[INFO] [stdout]   45:     0x70425c254a04 - clone
[INFO] [stdout]   46:                0x0 - <unknown>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout]     part2::tests::test_process
[INFO] [stdout] 
[INFO] [stdout] test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.05s
[INFO] [stdout] 
[INFO] [stderr] error: test failed, to rerun pass `-p day-03 --lib`
[INFO] running `Command { std: "docker" "inspect" "a659c67fd99eb0f2beef4258f8e0b46ddff7686ae97f3984bd95a87db039eb26", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "a659c67fd99eb0f2beef4258f8e0b46ddff7686ae97f3984bd95a87db039eb26", kill_on_drop: false }`
[INFO] [stdout] a659c67fd99eb0f2beef4258f8e0b46ddff7686ae97f3984bd95a87db039eb26
