[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#1ef7943ee607160a564655b6596f83670ef95df5 for pr-146098-6
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024" "/workspace/builds/worker-5-tc1/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-5-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-5-tc1/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/Siddid-Soni/advent-of-code-2024 on toolchain 1ef7943ee607160a564655b6596f83670ef95df5
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1ef7943ee607160a564655b6596f83670ef95df5" "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" "+1ef7943ee607160a564655b6596f83670ef95df5" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded code-timing-macros v0.0.5
[INFO] [stderr]   Downloaded cached_proc_macro_types v0.1.1
[INFO] [stderr]   Downloaded divan v0.1.17
[INFO] [stderr]   Downloaded cached_proc_macro v0.23.0
[INFO] [stderr]   Downloaded divan-macros v0.1.17
[INFO] [stderr]   Downloaded clap v4.5.23
[INFO] [stderr]   Downloaded terminal_size v0.4.1
[INFO] [stderr]   Downloaded cached v0.54.0
[INFO] [stderr]   Downloaded clap_builder v4.5.23
[INFO] [stderr]   Downloaded condtype v1.3.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+1ef7943ee607160a564655b6596f83670ef95df5" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] ad9303e234832b162136c95d0a92df4f0700dca72263d6def9e362f44f6fcef6
[INFO] running `Command { std: "docker" "start" "-a" "ad9303e234832b162136c95d0a92df4f0700dca72263d6def9e362f44f6fcef6", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "ad9303e234832b162136c95d0a92df4f0700dca72263d6def9e362f44f6fcef6", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "ad9303e234832b162136c95d0a92df4f0700dca72263d6def9e362f44f6fcef6", kill_on_drop: false }`
[INFO] [stdout] ad9303e234832b162136c95d0a92df4f0700dca72263d6def9e362f44f6fcef6
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+1ef7943ee607160a564655b6596f83670ef95df5" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] dd9d52d9246dd6181fe60adb67938927361e0fe26670b981eaedeffdad12ac25
[INFO] running `Command { std: "docker" "start" "-a" "dd9d52d9246dd6181fe60adb67938927361e0fe26670b981eaedeffdad12ac25", kill_on_drop: false }`
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part1.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr] warning: output filename collision at /opt/rustwide/target/debug/part2.dwp
[INFO] [stderr]   |
[INFO] [stderr]   = note: 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]   = note: this may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>
[INFO] [stderr]   = help: consider changing their names to be unique or compiling them separately
[INFO] [stderr]    Compiling fnv v1.0.7
[INFO] [stderr]    Compiling allocator-api2 v0.2.21
[INFO] [stderr]    Compiling cached_proc_macro_types v0.1.1
[INFO] [stderr]    Compiling ahash v0.8.11
[INFO] [stderr]    Compiling regex-automata v0.4.9
[INFO] [stderr]    Compiling syn v2.0.90
[INFO] [stderr]    Compiling hashbrown v0.14.5
[INFO] [stderr]    Compiling regex v1.11.1
[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 day-15 v0.1.0 (/opt/rustwide/workdir/day-15)
[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-22 v0.1.0 (/opt/rustwide/workdir/day-22)
[INFO] [stderr]    Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03)
[INFO] [stderr]    Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07)
[INFO] [stderr]    Compiling day-20 v0.1.0 (/opt/rustwide/workdir/day-20)
[INFO] [stderr]    Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04)
[INFO] [stderr]    Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10)
[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-09 v0.1.0 (/opt/rustwide/workdir/day-09)
[INFO] [stderr]    Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18)
[INFO] [stderr]    Compiling day-23 v0.1.0 (/opt/rustwide/workdir/day-23)
[INFO] [stderr]    Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06)
[INFO] [stderr]    Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12)
[INFO] [stderr]    Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13)
[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-02 v0.1.0 (/opt/rustwide/workdir/day-02)
[INFO] [stderr]    Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05)
[INFO] [stderr]    Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08)
[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-06/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-06/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-09/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-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-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-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-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-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-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/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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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] [stderr]    Compiling thiserror v1.0.69
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-06/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-06/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-09/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [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-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-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-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-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-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-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-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/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-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-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/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/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-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-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-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-03/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-03/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling darling_macro v0.20.10
[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 17.78s
[INFO] running `Command { std: "docker" "inspect" "dd9d52d9246dd6181fe60adb67938927361e0fe26670b981eaedeffdad12ac25", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "dd9d52d9246dd6181fe60adb67938927361e0fe26670b981eaedeffdad12ac25", kill_on_drop: false }`
[INFO] [stdout] dd9d52d9246dd6181fe60adb67938927361e0fe26670b981eaedeffdad12ac25
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+1ef7943ee607160a564655b6596f83670ef95df5" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 116f14f2653523f6afda9b887d8a8d560d7b24f7c0623ea093de8f336ebf38b5
[INFO] running `Command { std: "docker" "start" "-a" "116f14f2653523f6afda9b887d8a8d560d7b24f7c0623ea093de8f336ebf38b5", kill_on_drop: false }`
[INFO] [stderr]    Compiling rustix v0.38.41
[INFO] [stderr]    Compiling clap_lex v0.7.4
[INFO] [stderr]    Compiling condtype v1.3.0
[INFO] [stderr]    Compiling regex-lite v0.1.6
[INFO] [stderr]    Compiling divan-macros v0.1.17
[INFO] [stderr]    Compiling terminal_size v0.4.1
[INFO] [stderr]    Compiling clap_builder v4.5.23
[INFO] [stderr]    Compiling clap v4.5.23
[INFO] [stderr]    Compiling divan v0.1.17
[INFO] [stderr]    Compiling day-22 v0.1.0 (/opt/rustwide/workdir/day-22)
[INFO] [stderr]    Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03)
[INFO] [stderr]    Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07)
[INFO] [stderr]    Compiling day-23 v0.1.0 (/opt/rustwide/workdir/day-23)
[INFO] [stderr]    Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09)
[INFO] [stderr]    Compiling day-11 v0.1.0 (/opt/rustwide/workdir/day-11)
[INFO] [stderr]    Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12)
[INFO] [stderr]    Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01)
[INFO] [stderr]    Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02)
[INFO] [stderr]    Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06)
[INFO] [stderr]    Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13)
[INFO] [stderr]    Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16)
[INFO] [stderr]    Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19)
[INFO] [stderr]    Compiling day-15 v0.1.0 (/opt/rustwide/workdir/day-15)
[INFO] [stderr]    Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10)
[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-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/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-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-11/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-20 v0.1.0 (/opt/rustwide/workdir/day-20)
[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-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-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-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] [stderr]    Compiling day-21 v0.1.0 (/opt/rustwide/workdir/day-21)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-12/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14)
[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-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-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] [stderr]    Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17)
[INFO] [stderr]    Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08)
[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] [stderr]    Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05)
[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-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-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-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-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-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]    Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18)
[INFO] [stderr]    Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04)
[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-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-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-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-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-15/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-15/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-23/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-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-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/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-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-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-14/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-18/src/bin/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-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-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-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-04/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-04/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-16/src/bin/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-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-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-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-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-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-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] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 13.86s
[INFO] running `Command { std: "docker" "inspect" "116f14f2653523f6afda9b887d8a8d560d7b24f7c0623ea093de8f336ebf38b5", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "116f14f2653523f6afda9b887d8a8d560d7b24f7c0623ea093de8f336ebf38b5", kill_on_drop: false }`
[INFO] [stdout] 116f14f2653523f6afda9b887d8a8d560d7b24f7c0623ea093de8f336ebf38b5
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+1ef7943ee607160a564655b6596f83670ef95df5" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] 9fa5c4c12fdbb3cb55f5fc00e44de9658eaa52911654cace8f0b56da9b3d51ce
[INFO] running `Command { std: "docker" "start" "-a" "9fa5c4c12fdbb3cb55f5fc00e44de9658eaa52911654cace8f0b56da9b3d51ce", kill_on_drop: false }`
[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-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-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-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: 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-09/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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-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: `day-16` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-16` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-19` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-14` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-01` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-09` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-10` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-06` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-10` (bin "part2" test) generated 1 warning
[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-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-03/src/bin/part2.rs:6:18
[INFO] [stderr]   |
[INFO] [stderr] 6 |     let result = time_snippet!(process("day-03/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-12/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-23/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-23/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `day-12` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-13` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-03` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-12` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-23` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-15` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-23` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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-05/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-05/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-15/src/bin/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-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-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-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: `day-08` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-09` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-05` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-15` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-04` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-02` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-14` (bin "part2" 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-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-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-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-08/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-08/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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: `day-11` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-11` (bin "part2" 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-13` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-18` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-08` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-22` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-20` (bin "part2" test) generated 1 warning
[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-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-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-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: 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-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-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: `day-03` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-05` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-07` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-01` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-02` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-18` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-21` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-21/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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-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-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-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-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: `day-21` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-20` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-06` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-07` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-17` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-19` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-22` (bin "part2" test) generated 1 warning
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.12s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_01-3f106faf8a2a1bdb)
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test part1::tests::test_process ... ok
[INFO] [stdout] test part2::tests::test_process ... ok
[INFO] [stderr]      Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/deps/part1-1a673f96a2f4afe1)
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.03s
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/deps/part2-66093f1d2e4f832c)
[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_02-53d5365e7dc5f943)
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test part1::tests::test_process ... ok
[INFO] [stdout] test part2::tests::test_process ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/deps/part1-6a3158a11563c2ae)
[INFO] [stderr]      Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/deps/part2-d1c2ba7a2327eed9)
[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] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_03-5a07a1df8cc6cac9)
[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 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' (36) 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:     0x5aa6cad35972 - std::backtrace_rs::backtrace::libunwind::trace::h786de35fecf3582f
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/../../backtrace/src/backtrace/libunwind.rs:117:9
[INFO] [stdout]    1:     0x5aa6cad35972 - std::backtrace_rs::backtrace::trace_unsynchronized::h4a7da1a2a64387f1
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/../../backtrace/src/backtrace/mod.rs:66:14
[INFO] [stdout]    2:     0x5aa6cad35972 - std::sys::backtrace::_print_fmt::h6bd7d500070c788c
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/sys/backtrace.rs:66:9
[INFO] [stdout]    3:     0x5aa6cad35972 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h6d82c1afff976903
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/sys/backtrace.rs:39:26
[INFO] [stdout]    4:     0x5aa6cad4630f - core::fmt::rt::Argument::fmt::hc4ce6d643d397690
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/fmt/rt.rs:173:76
[INFO] [stdout]    5:     0x5aa6cad4630f - core::fmt::write::hb1e7ca88b6a3936e
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/fmt/mod.rs:1469:25
[INFO] [stdout]    6:     0x5aa6cad03313 - std::io::default_write_fmt::haffd49d96f1984a8
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/io/mod.rs:639:11
[INFO] [stdout]    7:     0x5aa6cad03313 - std::io::Write::write_fmt::h027871c57cf57c01
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/io/mod.rs:1954:13
[INFO] [stdout]    8:     0x5aa6cad0f1e2 - std::sys::backtrace::BacktraceLock::print::ha2430613ee79d059
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/sys/backtrace.rs:42:9
[INFO] [stdout]    9:     0x5aa6cad13cbf - std::panicking::default_hook::{{closure}}::hdbd2db9e5c303cf6
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:301:27
[INFO] [stdout]   10:     0x5aa6cad13b51 - std::panicking::default_hook::hed93c70cba5fdcf0
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:325:9
[INFO] [stdout]   11:     0x5aa6caa56f1e - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::hd0ee8b569efc6a07
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/alloc/src/boxed.rs:2099:9
[INFO] [stdout]   12:     0x5aa6caa56f1e - test::test_main_with_exit_callback::{{closure}}::hf10864b576ecd15d
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/test/src/lib.rs:145:21
[INFO] [stdout]   13:     0x5aa6cad142cf - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::h3a55ca34534c0d00
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/alloc/src/boxed.rs:2099:9
[INFO] [stdout]   14:     0x5aa6cad142cf - std::panicking::panic_with_hook::h3862d766c2cec19b
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:842:13
[INFO] [stdout]   15:     0x5aa6cad1412a - std::panicking::panic_handler::{{closure}}::hb95eb402b5e28ee1
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:707:13
[INFO] [stdout]   16:     0x5aa6cad0f319 - std::sys::backtrace::__rust_end_short_backtrace::hf73a26dc1835d85a
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/sys/backtrace.rs:174:18
[INFO] [stdout]   17:     0x5aa6cacf74ad - __rustc[6ed5915ee467787]::rust_begin_unwind
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:698:5
[INFO] [stdout]   18:     0x5aa6cad4ecf0 - core::panicking::panic_fmt::h3454303eb8e6f7cd
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/panicking.rs:80:14
[INFO] [stdout]   19:     0x5aa6cad4eaf3 - core::panicking::assert_failed_inner::hdcc703ae7c807131
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/panicking.rs:444:17
[INFO] [stdout]   20:     0x5aa6cad23460 - core::panicking::assert_failed::h7d833fa18a067295
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/panicking.rs:399:5
[INFO] [stdout]   21:     0x5aa6caa34fe9 - day_03::part2::tests::test_process::hb2ffb4fdbe5160b8
[INFO] [stdout]                                at /opt/rustwide/workdir/day-03/src/part2.rs:32:9
[INFO] [stdout]   22:     0x5aa6caa35007 - day_03::part2::tests::test_process::{{closure}}::he51274c0b8bed6eb
[INFO] [stdout]                                at /opt/rustwide/workdir/day-03/src/part2.rs:31:22
[INFO] [stdout]   23:     0x5aa6caa313f6 - core::ops::function::FnOnce::call_once::h48d5e67aba0ca12f
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   24:     0x5aa6caa56cfb - core::ops::function::FnOnce::call_once::ha729ee35d2fab541
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   25:     0x5aa6caa56cfb - test::__rust_begin_short_backtrace::ha40f4db8207e1111
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/test/src/lib.rs:663:18
[INFO] [stdout]   26:     0x5aa6caa6ad7d - test::run_test_in_process::{{closure}}::hc1b77cda5d44f0f3
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/test/src/lib.rs:686:74
[INFO] [stdout]   27:     0x5aa6caa6ad7d - <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::h1dbea1de64785521
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/panic/unwind_safe.rs:274:9
[INFO] [stdout]   28:     0x5aa6caa6ad7d - std::panicking::catch_unwind::do_call::hd5febe9affd5a1b3
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:590:40
[INFO] [stdout]   29:     0x5aa6caa6ad7d - std::panicking::catch_unwind::h51ea89627559b6f4
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:553:19
[INFO] [stdout]   30:     0x5aa6caa6ad7d - std::panic::catch_unwind::hb8b8c2367cae3d66
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panic.rs:359:14
[INFO] [stdout]   31:     0x5aa6caa6ad7d - test::run_test_in_process::ha5b55801407ea100
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/test/src/lib.rs:686:27
[INFO] [stdout]   32:     0x5aa6caa6ad7d - test::run_test::{{closure}}::h0b9d4072b527abf5
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/test/src/lib.rs:607:43
[INFO] [stdout]   33:     0x5aa6caa44294 - test::run_test::{{closure}}::hb1056b5731205822
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/test/src/lib.rs:637:41
[INFO] [stdout]   34:     0x5aa6caa44294 - std::sys::backtrace::__rust_begin_short_backtrace::hb61ff5a34023c7ef
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/sys/backtrace.rs:158:18
[INFO] [stdout]   35:     0x5aa6caa47bca - std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::hb0a83c0e8b353cff
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/thread/mod.rs:562:17
[INFO] [stdout]   36:     0x5aa6caa47bca - <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::hb4f32cb008535298
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/panic/unwind_safe.rs:274:9
[INFO] [stdout]   37:     0x5aa6caa47bca - std::panicking::catch_unwind::do_call::h16d110e4fc35789a
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:590:40
[INFO] [stdout]   38:     0x5aa6caa47bca - std::panicking::catch_unwind::hea9118f355699c4b
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panicking.rs:553:19
[INFO] [stdout]   39:     0x5aa6caa47bca - std::panic::catch_unwind::hf4b3c2a06d3f42f5
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/panic.rs:359:14
[INFO] [stdout]   40:     0x5aa6caa47bca - std::thread::Builder::spawn_unchecked_::{{closure}}::h3f4cb733a52d53d5
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/thread/mod.rs:560:30
[INFO] [stdout]   41:     0x5aa6caa47bca - core::ops::function::FnOnce::call_once{{vtable.shim}}::h4052f0967b37caeb
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   42:     0x5aa6cad0a71f - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h7ec433abd3f148b4
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/alloc/src/boxed.rs:2085:9
[INFO] [stdout]   43:     0x5aa6cad0a71f - std::sys::thread::unix::Thread::new::thread_start::he514622d3d7ba65c
[INFO] [stdout]                                at /rustc/1ef7943ee607160a564655b6596f83670ef95df5/library/std/src/sys/thread/unix.rs:124:17
[INFO] [stdout]   44:     0x7e2d34f73aa4 - <unknown>
[INFO] [stdout]   45:     0x7e2d35000a64 - clone
[INFO] [stdout]   46:                0x0 - <unknown>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout]     part2::tests::test_process
[INFO] [stdout] 
[INFO] [stdout] test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.03s
[INFO] [stdout] 
[INFO] [stderr] error: test failed, to rerun pass `-p day-03 --lib`
[INFO] running `Command { std: "docker" "inspect" "9fa5c4c12fdbb3cb55f5fc00e44de9658eaa52911654cace8f0b56da9b3d51ce", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "9fa5c4c12fdbb3cb55f5fc00e44de9658eaa52911654cace8f0b56da9b3d51ce", kill_on_drop: false }`
[INFO] [stdout] 9fa5c4c12fdbb3cb55f5fc00e44de9658eaa52911654cace8f0b56da9b3d51ce
