[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 master#d98a5da813da67eb189387b8ccfb73cf481275d8+rustflags=-Copt-level=3 for pr-138759
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024" "/workspace/builds/worker-6-tc1/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-6-tc1/source'...
[INFO] [stderr] done.
[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-6-tc1/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/Siddid-Soni/advent-of-code-2024 on toolchain d98a5da813da67eb189387b8ccfb73cf481275d8
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[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" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded libc v0.2.167
[INFO] [stderr]   Downloaded cached_proc_macro v0.23.0
[INFO] [stderr]   Downloaded code-timing-macros v0.0.5
[INFO] [stderr]   Downloaded divan-macros v0.1.17
[INFO] [stderr]   Downloaded divan v0.1.17
[INFO] [stderr]   Downloaded cached v0.54.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 22b9a5169ee1f90e22fbf45a85747d454a5a4014441a98f7d438914afb717eb3
[INFO] running `Command { std: "docker" "start" "-a" "22b9a5169ee1f90e22fbf45a85747d454a5a4014441a98f7d438914afb717eb3", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "22b9a5169ee1f90e22fbf45a85747d454a5a4014441a98f7d438914afb717eb3", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "22b9a5169ee1f90e22fbf45a85747d454a5a4014441a98f7d438914afb717eb3", kill_on_drop: false }`
[INFO] [stdout] 22b9a5169ee1f90e22fbf45a85747d454a5a4014441a98f7d438914afb717eb3
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Copt-level=3" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] cc054dcc7e03f0f253904dd1350bec1acc9fc5c8c7557184df49f32d0de57fac
[INFO] running `Command { std: "docker" "start" "-a" "cc054dcc7e03f0f253904dd1350bec1acc9fc5c8c7557184df49f32d0de57fac", 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 zerocopy v0.7.35
[INFO] [stderr]    Compiling web-time v1.1.0
[INFO] [stderr]    Compiling cached_proc_macro_types v0.1.1
[INFO] [stderr]    Compiling proc-macro2 v1.0.92
[INFO] [stderr]    Compiling ahash v0.8.11
[INFO] [stderr]    Compiling quote v1.0.37
[INFO] [stderr]    Compiling hashbrown v0.14.5
[INFO] [stderr]    Compiling syn v2.0.90
[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 darling_macro v0.20.10
[INFO] [stderr]    Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09)
[INFO] [stderr]    Compiling day-20 v0.1.0 (/opt/rustwide/workdir/day-20)
[INFO] [stderr]    Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07)
[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] [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-04 v0.1.0 (/opt/rustwide/workdir/day-04)
[INFO] [stderr]    Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17)
[INFO] [stderr]    Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19)
[INFO] [stderr]    Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08)
[INFO] [stderr]    Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16)
[INFO] [stderr]    Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18)
[INFO] [stderr]    Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05)
[INFO] [stderr]    Compiling day-23 v0.1.0 (/opt/rustwide/workdir/day-23)
[INFO] [stderr]    Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02)
[INFO] [stderr]    Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01)
[INFO] [stderr]    Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10)
[INFO] [stderr]    Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03)
[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-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/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-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-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-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-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-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-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-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-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-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-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-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] [stderr]    Compiling thiserror v1.0.69
[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-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-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-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-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-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-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-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-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-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-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-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] [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-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-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-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-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-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-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-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-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-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/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-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-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-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-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-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/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] [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/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-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] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 18s
[INFO] running `Command { std: "docker" "inspect" "cc054dcc7e03f0f253904dd1350bec1acc9fc5c8c7557184df49f32d0de57fac", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "cc054dcc7e03f0f253904dd1350bec1acc9fc5c8c7557184df49f32d0de57fac", kill_on_drop: false }`
[INFO] [stdout] cc054dcc7e03f0f253904dd1350bec1acc9fc5c8c7557184df49f32d0de57fac
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Copt-level=3" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 1c8516739831d4849f92edae3c63eea14346484580c0f787682a7a7885d65166
[INFO] running `Command { std: "docker" "start" "-a" "1c8516739831d4849f92edae3c63eea14346484580c0f787682a7a7885d65166", kill_on_drop: false }`
[INFO] [stderr]    Compiling rustix v0.38.41
[INFO] [stderr]    Compiling linux-raw-sys v0.4.14
[INFO] [stderr]    Compiling libc v0.2.167
[INFO] [stderr]    Compiling divan-macros v0.1.17
[INFO] [stderr]    Compiling condtype v1.3.0
[INFO] [stderr]    Compiling regex-lite v0.1.6
[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-11 v0.1.0 (/opt/rustwide/workdir/day-11)
[INFO] [stderr]    Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04)
[INFO] [stderr]    Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09)
[INFO] [stderr]    Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06)
[INFO] [stderr]    Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17)
[INFO] [stderr]    Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12)
[INFO] [stderr]    Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18)
[INFO] [stderr]    Compiling day-21 v0.1.0 (/opt/rustwide/workdir/day-21)
[INFO] [stderr]    Compiling day-22 v0.1.0 (/opt/rustwide/workdir/day-22)
[INFO] [stderr]    Compiling day-23 v0.1.0 (/opt/rustwide/workdir/day-23)
[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/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-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-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-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-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-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-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-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-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] [stderr]    Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16)
[INFO] [stderr]    Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01)
[INFO] [stderr]    Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14)
[INFO] [stderr]    Compiling day-20 v0.1.0 (/opt/rustwide/workdir/day-20)
[INFO] [stderr]    Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19)
[INFO] [stderr]    Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03)
[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-13 v0.1.0 (/opt/rustwide/workdir/day-13)
[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-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-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-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-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-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-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-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] [stderr]    Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08)
[INFO] [stderr]    Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05)
[INFO] [stderr]    Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07)
[INFO] [stderr]    Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10)
[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-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-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-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-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-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] [stderr]    Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02)
[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] [stderr]    Compiling day-15 v0.1.0 (/opt/rustwide/workdir/day-15)
[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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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] [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-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-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] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 45.45s
[INFO] running `Command { std: "docker" "inspect" "1c8516739831d4849f92edae3c63eea14346484580c0f787682a7a7885d65166", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "1c8516739831d4849f92edae3c63eea14346484580c0f787682a7a7885d65166", kill_on_drop: false }`
[INFO] [stdout] 1c8516739831d4849f92edae3c63eea14346484580c0f787682a7a7885d65166
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Copt-level=3" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d98a5da813da67eb189387b8ccfb73cf481275d8" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] db57374011f5fdea679ef21f076f64be37bf922df2cddc5a23d4b4d76abf3d18
[INFO] running `Command { std: "docker" "start" "-a" "db57374011f5fdea679ef21f076f64be37bf922df2cddc5a23d4b4d76abf3d18", kill_on_drop: false }`
[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: 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-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-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-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-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-03` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-02` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-19` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-16` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-13` (bin "part1" 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-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-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: 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-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-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-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-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-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: `day-16` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-18` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-01` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-18` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-06` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-15` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-22` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-08` (bin "part2" test) generated 1 warning
[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: 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-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-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-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-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-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-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-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: `day-08` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-05` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-09` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-20` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-02` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-10` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-22` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-07` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-12` (bin "part1" test) generated 1 warning
[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-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-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-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] [stderr]  --> day-01/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[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: `day-11` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-11` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-13` (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: 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-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-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-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-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-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-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: 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-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-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: `day-07` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-06` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-17` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-14` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-04` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-17` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-04` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-21` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-10` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-09` (bin "part1" test) generated 1 warning
[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-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-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-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-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: 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-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-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: `day-15` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-12` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-20` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-03` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-23` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-21` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-19` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-23` (bin "part2" test) generated 1 warning
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.15s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_01-bc4784a862a494d6)
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test part2::tests::test_process ... ok
[INFO] [stdout] test part1::tests::test_process ... ok
[INFO] [stderr]      Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/deps/part1-6e7358e890f19520)
[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] [stderr]      Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/deps/part2-1686cbb1f9ca85d5)
[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/lib.rs (/opt/rustwide/target/debug/deps/day_02-20003cc9cc512b85)
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test part2::tests::test_process ... ok
[INFO] [stdout] test part1::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-5d0fcd62492039b7)
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/deps/part2-b2f9399dd3604bd4)
[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] [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-168ea9ecaeb8fba1)
[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:     0x56ba3645e8b2 - std::backtrace_rs::backtrace::libunwind::trace::hd39b1f53d3cf9745
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/../../backtrace/src/backtrace/libunwind.rs:117:9
[INFO] [stdout]    1:     0x56ba3645e8b2 - std::backtrace_rs::backtrace::trace_unsynchronized::he91d9a75d4e3972b
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/../../backtrace/src/backtrace/mod.rs:66:14
[INFO] [stdout]    2:     0x56ba3645e8b2 - std::sys::backtrace::_print_fmt::hca46938f8c6e22cf
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/sys/backtrace.rs:66:9
[INFO] [stdout]    3:     0x56ba3645e8b2 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::ha499add612cccf8e
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/sys/backtrace.rs:39:26
[INFO] [stdout]    4:     0x56ba364845c3 - core::fmt::rt::Argument::fmt::hd21145b75a833b7a
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/fmt/rt.rs:173:76
[INFO] [stdout]    5:     0x56ba364845c3 - core::fmt::write::hb10c956f5235c8a4
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/fmt/mod.rs:1465:25
[INFO] [stdout]    6:     0x56ba3645ba93 - std::io::default_write_fmt::hdb7615052be2ba4d
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/io/mod.rs:639:11
[INFO] [stdout]    7:     0x56ba3645ba93 - std::io::Write::write_fmt::he1bcd251ec6e4153
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/io/mod.rs:1954:13
[INFO] [stdout]    8:     0x56ba3645e702 - std::sys::backtrace::BacktraceLock::print::hb47c770ef659fd10
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/sys/backtrace.rs:42:9
[INFO] [stdout]    9:     0x56ba3645fe1c - std::panicking::default_hook::{{closure}}::hdda8afb9d457a22c
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:300:27
[INFO] [stdout]   10:     0x56ba3645fc72 - std::panicking::default_hook::h7c46b44874fe5c9a
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:324:9
[INFO] [stdout]   11:     0x56ba36359f94 - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::h178a5fcedee41e2f
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/alloc/src/boxed.rs:1985:9
[INFO] [stdout]   12:     0x56ba36359f94 - test::test_main_with_exit_callback::{{closure}}::h951a41e0149d6d5d
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/test/src/lib.rs:145:21
[INFO] [stdout]   13:     0x56ba364607fb - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::h13602080f5b63276
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/alloc/src/boxed.rs:1985:9
[INFO] [stdout]   14:     0x56ba364607fb - std::panicking::rust_panic_with_hook::ha6cb99ed099eb1c5
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:841:13
[INFO] [stdout]   15:     0x56ba364605ca - std::panicking::begin_panic_handler::{{closure}}::he11808bc797ee921
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:706:13
[INFO] [stdout]   16:     0x56ba3645eda9 - std::sys::backtrace::__rust_end_short_backtrace::h9418807cb7346258
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/sys/backtrace.rs:168:18
[INFO] [stdout]   17:     0x56ba3646025d - __rustc[18fb429eef004894]::rust_begin_unwind
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:697:5
[INFO] [stdout]   18:     0x56ba36482e00 - core::panicking::panic_fmt::hd890aeb12c3a3fc3
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/panicking.rs:75:14
[INFO] [stdout]   19:     0x56ba36483097 - core::panicking::assert_failed_inner::h02e1528dd7bc6647
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/panicking.rs:448:17
[INFO] [stdout]   20:     0x56ba36440cf6 - core::panicking::assert_failed::h8d7cc7a1e1cfc347
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/panicking.rs:403:5
[INFO] [stdout]   21:     0x56ba3631c5e1 - day_03::part2::tests::test_process::h0d85dd1671097051
[INFO] [stdout]                                at /opt/rustwide/workdir/day-03/src/part2.rs:32:9
[INFO] [stdout]   22:     0x56ba3631c5e1 - day_03::part2::tests::test_process::{{closure}}::hefd58bf0a4577ccf
[INFO] [stdout]                                at /opt/rustwide/workdir/day-03/src/part2.rs:31:22
[INFO] [stdout]   23:     0x56ba3631c5e1 - core::ops::function::FnOnce::call_once::h95e678edccf704bd
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   24:     0x56ba3635f71b - core::ops::function::FnOnce::call_once::h2869fb5b0a2b0bdc
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   25:     0x56ba3635f71b - test::__rust_begin_short_backtrace::h7dd7142bd62fa711
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/test/src/lib.rs:648:18
[INFO] [stdout]   26:     0x56ba3635e90e - test::run_test_in_process::{{closure}}::h43a753f038d36b3f
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/test/src/lib.rs:671:74
[INFO] [stdout]   27:     0x56ba3635e90e - <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::h0ca95dd3e12d1e16
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/panic/unwind_safe.rs:272:9
[INFO] [stdout]   28:     0x56ba3635e90e - std::panicking::catch_unwind::do_call::he308587d70ac34ba
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:589:40
[INFO] [stdout]   29:     0x56ba3635e90e - std::panicking::catch_unwind::h30dcba31973e8fb0
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:552:19
[INFO] [stdout]   30:     0x56ba3635e90e - std::panic::catch_unwind::hfb68364e5621fbee
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panic.rs:359:14
[INFO] [stdout]   31:     0x56ba3635e90e - test::run_test_in_process::hcdcc2977903b998a
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/test/src/lib.rs:671:27
[INFO] [stdout]   32:     0x56ba3635e90e - test::run_test::{{closure}}::h544a6550958c5d14
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/test/src/lib.rs:592:43
[INFO] [stdout]   33:     0x56ba36322484 - test::run_test::{{closure}}::hb172e48ebe2b92c7
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/test/src/lib.rs:622:41
[INFO] [stdout]   34:     0x56ba36322484 - std::sys::backtrace::__rust_begin_short_backtrace::h7e79d8706638bea0
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/sys/backtrace.rs:152:18
[INFO] [stdout]   35:     0x56ba36325e5a - std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::hc4a275f1e71b8ab0
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/thread/mod.rs:559:17
[INFO] [stdout]   36:     0x56ba36325e5a - <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::h01ed0d242df78cfd
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/panic/unwind_safe.rs:272:9
[INFO] [stdout]   37:     0x56ba36325e5a - std::panicking::catch_unwind::do_call::h052f373fb905fee0
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:589:40
[INFO] [stdout]   38:     0x56ba36325e5a - std::panicking::catch_unwind::hb425d20c8ffb09c8
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panicking.rs:552:19
[INFO] [stdout]   39:     0x56ba36325e5a - std::panic::catch_unwind::ha0d5dfbf18fdeda5
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/panic.rs:359:14
[INFO] [stdout]   40:     0x56ba36325e5a - std::thread::Builder::spawn_unchecked_::{{closure}}::hbe79182bd37949c7
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/thread/mod.rs:557:30
[INFO] [stdout]   41:     0x56ba36325e5a - core::ops::function::FnOnce::call_once{{vtable.shim}}::hc096c4a06972fde5
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   42:     0x56ba36463757 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h47377e27fb938a26
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/alloc/src/boxed.rs:1971:9
[INFO] [stdout]   43:     0x56ba36463757 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h72f1fe5d095abf57
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/alloc/src/boxed.rs:1971:9
[INFO] [stdout]   44:     0x56ba36463757 - std::sys::pal::unix::thread::Thread::new::thread_start::h0a4d8e1b9c0d38cf
[INFO] [stdout]                                at /rustc/d98a5da813da67eb189387b8ccfb73cf481275d8/library/std/src/sys/pal/unix/thread.rs:97:17
[INFO] [stdout]   45:     0x76fa60dfeaa4 - <unknown>
[INFO] [stdout]   46:     0x76fa60e8ba34 - clone
[INFO] [stdout]   47:                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.09s
[INFO] [stdout] 
[INFO] [stderr] error: test failed, to rerun pass `-p day-03 --lib`
[INFO] running `Command { std: "docker" "inspect" "db57374011f5fdea679ef21f076f64be37bf922df2cddc5a23d4b4d76abf3d18", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "db57374011f5fdea679ef21f076f64be37bf922df2cddc5a23d4b4d76abf3d18", kill_on_drop: false }`
[INFO] [stdout] db57374011f5fdea679ef21f076f64be37bf922df2cddc5a23d4b4d76abf3d18
