[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 try#bd7d74411512a3dd3b35d2f699c51dd2557c7e7e+cargoflags=-Zbuild-dir-new-layout for pr-149852-1
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024" "/workspace/builds/worker-0-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-0-tc2/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-0-tc2/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/Siddid-Soni/advent-of-code-2024 on toolchain bd7d74411512a3dd3b35d2f699c51dd2557c7e7e
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+bd7d74411512a3dd3b35d2f699c51dd2557c7e7e" "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" "+bd7d74411512a3dd3b35d2f699c51dd2557c7e7e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:aa71247004a7fa38d13ec170f48f06cdedf5bc50b2a8645e56ed7e992e6fa513" "/opt/rustwide/cargo-home/bin/cargo" "+bd7d74411512a3dd3b35d2f699c51dd2557c7e7e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] e400d4b70e23b7bfa3faf851405c3042966ed827095dddba658020766b327fd9
[INFO] running `Command { std: "docker" "start" "-a" "e400d4b70e23b7bfa3faf851405c3042966ed827095dddba658020766b327fd9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "e400d4b70e23b7bfa3faf851405c3042966ed827095dddba658020766b327fd9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "e400d4b70e23b7bfa3faf851405c3042966ed827095dddba658020766b327fd9", kill_on_drop: false }`
[INFO] [stdout] e400d4b70e23b7bfa3faf851405c3042966ed827095dddba658020766b327fd9
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-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:aa71247004a7fa38d13ec170f48f06cdedf5bc50b2a8645e56ed7e992e6fa513" "/opt/rustwide/cargo-home/bin/cargo" "+bd7d74411512a3dd3b35d2f699c51dd2557c7e7e" "build" "--frozen" "--message-format=json" "-Zbuild-dir-new-layout", kill_on_drop: false }`
[INFO] [stdout] 0aebb3b2afbdefda6e8aae4ae6e6aa7e6b1a1e0c87e6324dbcd76290ae80ece5
[INFO] running `Command { std: "docker" "start" "-a" "0aebb3b2afbdefda6e8aae4ae6e6aa7e6b1a1e0c87e6324dbcd76290ae80ece5", 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 proc-macro2 v1.0.92
[INFO] [stderr]    Compiling cached_proc_macro_types v0.1.1
[INFO] [stderr]    Compiling regex-automata v0.4.9
[INFO] [stderr]    Compiling hashbrown v0.14.5
[INFO] [stderr]    Compiling quote v1.0.37
[INFO] [stderr]    Compiling syn v2.0.90
[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-09 v0.1.0 (/opt/rustwide/workdir/day-09)
[INFO] [stderr]    Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08)
[INFO] [stderr]    Compiling day-15 v0.1.0 (/opt/rustwide/workdir/day-15)
[INFO] [stderr]    Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04)
[INFO] [stderr]    Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17)
[INFO] [stderr]    Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19)
[INFO] [stderr]    Compiling day-20 v0.1.0 (/opt/rustwide/workdir/day-20)
[INFO] [stderr]    Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06)
[INFO] [stderr]    Compiling day-21 v0.1.0 (/opt/rustwide/workdir/day-21)
[INFO] [stderr]    Compiling day-23 v0.1.0 (/opt/rustwide/workdir/day-23)
[INFO] [stderr]    Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05)
[INFO] [stderr]    Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18)
[INFO] [stderr]    Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10)
[INFO] [stderr]    Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13)
[INFO] [stderr]    Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02)
[INFO] [stderr]    Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01)
[INFO] [stderr]    Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12)
[INFO] [stderr]    Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07)
[INFO] [stderr]    Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14)
[INFO] [stderr]    Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03)
[INFO] [stderr]    Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16)
[INFO] [stderr]    Compiling day-22 v0.1.0 (/opt/rustwide/workdir/day-22)
[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/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-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-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-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-05/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-05/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-22/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-22/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-17/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process());
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-14/src/bin/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-12/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-12/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-02/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-02/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-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-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-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-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-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-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-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-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-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-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-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-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-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-21/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-21/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-21/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-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-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-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-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-01/src/bin/part2.rs:6:18
[INFO] [stdout]   |
[INFO] [stdout] 6 |     let result = time_snippet!(process("day-01/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-09/src/bin/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/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-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-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-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-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-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-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-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-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-13/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling thiserror v1.0.69
[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.49s
[INFO] running `Command { std: "docker" "inspect" "0aebb3b2afbdefda6e8aae4ae6e6aa7e6b1a1e0c87e6324dbcd76290ae80ece5", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "0aebb3b2afbdefda6e8aae4ae6e6aa7e6b1a1e0c87e6324dbcd76290ae80ece5", kill_on_drop: false }`
[INFO] [stdout] 0aebb3b2afbdefda6e8aae4ae6e6aa7e6b1a1e0c87e6324dbcd76290ae80ece5
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-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:aa71247004a7fa38d13ec170f48f06cdedf5bc50b2a8645e56ed7e992e6fa513" "/opt/rustwide/cargo-home/bin/cargo" "+bd7d74411512a3dd3b35d2f699c51dd2557c7e7e" "test" "--frozen" "--no-run" "--message-format=json" "-Zbuild-dir-new-layout", kill_on_drop: false }`
[INFO] [stdout] fa13af03f8568936d6c294fe883e223175b6b9ebf4bb85983d4a88db9d5fe75d
[INFO] running `Command { std: "docker" "start" "-a" "fa13af03f8568936d6c294fe883e223175b6b9ebf4bb85983d4a88db9d5fe75d", kill_on_drop: false }`
[INFO] [stderr]    Compiling rustix v0.38.41
[INFO] [stderr]    Compiling libc v0.2.167
[INFO] [stderr]    Compiling regex-lite v0.1.6
[INFO] [stderr]    Compiling condtype v1.3.0
[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-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-06 v0.1.0 (/opt/rustwide/workdir/day-06)
[INFO] [stderr]    Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09)
[INFO] [stderr]    Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05)
[INFO] [stderr]    Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18)
[INFO] [stderr]    Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01)
[INFO] [stderr]    Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07)
[INFO] [stderr]    Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19)
[INFO] [stderr]    Compiling day-23 v0.1.0 (/opt/rustwide/workdir/day-23)
[INFO] [stderr]    Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02)
[INFO] [stderr]    Compiling day-22 v0.1.0 (/opt/rustwide/workdir/day-22)
[INFO] [stderr]    Compiling day-11 v0.1.0 (/opt/rustwide/workdir/day-11)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-10/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-10/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-06/src/bin/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-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-11/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-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-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-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-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/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] [stderr]    Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16)
[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-22/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-22/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-15 v0.1.0 (/opt/rustwide/workdir/day-15)
[INFO] [stderr]    Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08)
[INFO] [stderr]    Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12)
[INFO] [stderr]    Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17)
[INFO] [stderr]    Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-15/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-15/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-08/src/bin/part1.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-08/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-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-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-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] [stderr]    Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03)
[INFO] [stdout] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stdout]  --> day-13/src/bin/part2.rs:5:18
[INFO] [stdout]   |
[INFO] [stdout] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stdout]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: no expected values for `feature`
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04)
[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-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-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] [stderr]    Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14)
[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-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/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/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-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 day-20 v0.1.0 (/opt/rustwide/workdir/day-20)
[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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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]     Finished `test` profile [unoptimized + debuginfo] target(s) in 10.51s
[INFO] running `Command { std: "docker" "inspect" "fa13af03f8568936d6c294fe883e223175b6b9ebf4bb85983d4a88db9d5fe75d", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "fa13af03f8568936d6c294fe883e223175b6b9ebf4bb85983d4a88db9d5fe75d", kill_on_drop: false }`
[INFO] [stdout] fa13af03f8568936d6c294fe883e223175b6b9ebf4bb85983d4a88db9d5fe75d
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-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:aa71247004a7fa38d13ec170f48f06cdedf5bc50b2a8645e56ed7e992e6fa513" "/opt/rustwide/cargo-home/bin/cargo" "+bd7d74411512a3dd3b35d2f699c51dd2557c7e7e" "test" "--frozen" "-Zbuild-dir-new-layout", kill_on_drop: false }`
[INFO] [stdout] 8c6d0336002b291c86871fae32e874425b55de19e217df27b518aeff733463ae
[INFO] running `Command { std: "docker" "start" "-a" "8c6d0336002b291c86871fae32e874425b55de19e217df27b518aeff733463ae", kill_on_drop: false }`
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-23/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-23/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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-10/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-10/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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-13/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-13/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-14/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: 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: `day-23` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-01` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-05` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-10` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-15` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-08` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-13` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-14` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-21` (bin "part2" test) generated 1 warning
[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-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-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-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-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-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: `day-12` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-03` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-03` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-06` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-04` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-16` (bin "part1" test) generated 1 warning
[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-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-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-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-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-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-17` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-23` (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-07` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-20` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-22` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-11/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-11/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-11/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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-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-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-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-09/src/bin/part1.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-09/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `day-11` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-11` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-10` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-18` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-07` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-02` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-01` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-09` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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-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/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/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-14/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-20/src/bin/part2.rs:5:18
[INFO] [stderr]   |
[INFO] [stderr] 5 |     let result = time_snippet!(process("day-20/input1.txt"));
[INFO] [stderr]   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]   = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]   = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `tracing`
[INFO] [stderr]  --> day-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-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-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-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-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: `day-12` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-19` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-17` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-19` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-14` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-20` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-16` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-13` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-22` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-02` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-09` (bin "part2" test) generated 1 warning
[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-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-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-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-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-06` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-08` (bin "part2" test) generated 1 warning
[INFO] [stderr] warning: `day-18` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-04` (bin "part1" test) generated 1 warning
[INFO] [stderr] warning: `day-21` (bin "part1" test) generated 1 warning
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.15s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/build/day-01/e899ebe3c503b9dd/deps/day_01-e899ebe3c503b9dd)
[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] [stderr]      Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/build/day-01/0a2d9bffd55e5513/deps/part1-0a2d9bffd55e5513)
[INFO] [stdout] test result: ok. 2 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/bin/part2.rs (/opt/rustwide/target/debug/build/day-01/9223bbdcbbe7d9ec/deps/part2-9223bbdcbbe7d9ec)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/build/day-02/101217bcc1720db4/deps/day_02-101217bcc1720db4)
[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] [stderr]      Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/build/day-02/f1d8eb2acca360be/deps/part1-f1d8eb2acca360be)
[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] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/build/day-02/aeb7c5a2a52519ee/deps/part2-aeb7c5a2a52519ee)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/build/day-03/7940180f586ebb7b/deps/day_03-7940180f586ebb7b)
[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' (35) 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:     0x5c38237d3552 - std[840933623431fd06]::backtrace_rs::backtrace::libunwind::trace
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/../../backtrace/src/backtrace/libunwind.rs:117:9
[INFO] [stdout]    1:     0x5c38237d3552 - std[840933623431fd06]::backtrace_rs::backtrace::trace_unsynchronized::<std[840933623431fd06]::sys::backtrace::_print_fmt::{closure#1}>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/../../backtrace/src/backtrace/mod.rs:66:14
[INFO] [stdout]    2:     0x5c38237d3552 - std[840933623431fd06]::sys::backtrace::_print_fmt
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/sys/backtrace.rs:74:9
[INFO] [stdout]    3:     0x5c38237d3552 - <<std[840933623431fd06]::sys::backtrace::BacktraceLock>::print::DisplayBacktrace as core[8f93d80df273fe75]::fmt::Display>::fmt
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/sys/backtrace.rs:44:26
[INFO] [stdout]    4:     0x5c38237e920a - <core[8f93d80df273fe75]::fmt::rt::Argument>::fmt
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/fmt/rt.rs:152:76
[INFO] [stdout]    5:     0x5c38237e920a - core[8f93d80df273fe75]::fmt::write
[INFO] [stdout]    6:     0x5c38237d8386 - std[840933623431fd06]::io::default_write_fmt::<alloc[40b2bae28975ac47]::vec::Vec<u8>>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/io/mod.rs:639:11
[INFO] [stdout]    7:     0x5c38237d8386 - <alloc[40b2bae28975ac47]::vec::Vec<u8> as std[840933623431fd06]::io::Write>::write_fmt
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/io/mod.rs:1994:13
[INFO] [stdout]    8:     0x5c38237b167f - <std[840933623431fd06]::sys::backtrace::BacktraceLock>::print
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/sys/backtrace.rs:47:9
[INFO] [stdout]    9:     0x5c38237b167f - std[840933623431fd06]::panicking::default_hook::{closure#0}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:292:27
[INFO] [stdout]   10:     0x5c38237cb4e9 - std[840933623431fd06]::panicking::default_hook
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:316:9
[INFO] [stdout]   11:     0x5c38234f1b0e - <alloc[40b2bae28975ac47]::boxed::Box<dyn for<'a, 'b> core[8f93d80df273fe75]::ops::function::Fn<(&'a std[840933623431fd06]::panic::PanicHookInfo<'b>,), Output = ()> + core[8f93d80df273fe75]::marker::Sync + core[8f93d80df273fe75]::marker::Send> as core[8f93d80df273fe75]::ops::function::Fn<(&std[840933623431fd06]::panic::PanicHookInfo,)>>::call
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/alloc/src/boxed.rs:2220:9
[INFO] [stdout]   12:     0x5c38234f1b0e - test[2f1252070343a163]::test_main_with_exit_callback::<test[2f1252070343a163]::test_main::{closure#0}>::{closure#0}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/test/src/lib.rs:145:21
[INFO] [stdout]   13:     0x5c38237cb6a2 - <alloc[40b2bae28975ac47]::boxed::Box<dyn for<'a, 'b> core[8f93d80df273fe75]::ops::function::Fn<(&'a std[840933623431fd06]::panic::PanicHookInfo<'b>,), Output = ()> + core[8f93d80df273fe75]::marker::Sync + core[8f93d80df273fe75]::marker::Send> as core[8f93d80df273fe75]::ops::function::Fn<(&std[840933623431fd06]::panic::PanicHookInfo,)>>::call
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/alloc/src/boxed.rs:2220:9
[INFO] [stdout]   14:     0x5c38237cb6a2 - std[840933623431fd06]::panicking::panic_with_hook
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:833:13
[INFO] [stdout]   15:     0x5c38237b1738 - std[840933623431fd06]::panicking::panic_handler::{closure#0}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:698:13
[INFO] [stdout]   16:     0x5c38237a9009 - std[840933623431fd06]::sys::backtrace::__rust_end_short_backtrace::<std[840933623431fd06]::panicking::panic_handler::{closure#0}, !>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/sys/backtrace.rs:182:18
[INFO] [stdout]   17:     0x5c38237b258d - __rustc[5b4a0c6d8cc4a177]::rust_begin_unwind
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:689:5
[INFO] [stdout]   18:     0x5c38237e99cc - core[8f93d80df273fe75]::panicking::panic_fmt
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/panicking.rs:80:14
[INFO] [stdout]   19:     0x5c38237e9883 - core[8f93d80df273fe75]::panicking::assert_failed_inner
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/panicking.rs:439:17
[INFO] [stdout]   20:     0x5c38237a67a5 - core[8f93d80df273fe75]::panicking::assert_failed::<i32, i32>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/panicking.rs:394:5
[INFO] [stdout]   21:     0x5c38234e401f - day_03[996a44072e1bf2aa]::part2::tests::test_process
[INFO] [stdout]                                at /opt/rustwide/workdir/day-03/src/part2.rs:32:9
[INFO] [stdout]   22:     0x5c38234e1be7 - day_03[996a44072e1bf2aa]::part2::tests::test_process::{closure#0}
[INFO] [stdout]                                at /opt/rustwide/workdir/day-03/src/part2.rs:31:22
[INFO] [stdout]   23:     0x5c38234e5e06 - <day_03[996a44072e1bf2aa]::part2::tests::test_process::{closure#0} as core[8f93d80df273fe75]::ops::function::FnOnce<()>>::call_once
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   24:     0x5c38234e5ebb - <fn() -> core[8f93d80df273fe75]::result::Result<(), alloc[40b2bae28975ac47]::string::String> as core[8f93d80df273fe75]::ops::function::FnOnce<()>>::call_once
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   25:     0x5c38234e5ebb - test[2f1252070343a163]::__rust_begin_short_backtrace::<core[8f93d80df273fe75]::result::Result<(), alloc[40b2bae28975ac47]::string::String>, fn() -> core[8f93d80df273fe75]::result::Result<(), alloc[40b2bae28975ac47]::string::String>>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/test/src/lib.rs:663:18
[INFO] [stdout]   26:     0x5c38234f271a - test[2f1252070343a163]::run_test_in_process::{closure#0}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/test/src/lib.rs:686:74
[INFO] [stdout]   27:     0x5c38234f271a - <core[8f93d80df273fe75]::panic::unwind_safe::AssertUnwindSafe<test[2f1252070343a163]::run_test_in_process::{closure#0}> as core[8f93d80df273fe75]::ops::function::FnOnce<()>>::call_once
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/panic/unwind_safe.rs:274:9
[INFO] [stdout]   28:     0x5c38234f271a - std[840933623431fd06]::panicking::catch_unwind::do_call::<core[8f93d80df273fe75]::panic::unwind_safe::AssertUnwindSafe<test[2f1252070343a163]::run_test_in_process::{closure#0}>, core[8f93d80df273fe75]::result::Result<(), alloc[40b2bae28975ac47]::string::String>>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:581:40
[INFO] [stdout]   29:     0x5c38234f271a - std[840933623431fd06]::panicking::catch_unwind::<core[8f93d80df273fe75]::result::Result<(), alloc[40b2bae28975ac47]::string::String>, core[8f93d80df273fe75]::panic::unwind_safe::AssertUnwindSafe<test[2f1252070343a163]::run_test_in_process::{closure#0}>>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:544:19
[INFO] [stdout]   30:     0x5c38234f271a - std[840933623431fd06]::panic::catch_unwind::<core[8f93d80df273fe75]::panic::unwind_safe::AssertUnwindSafe<test[2f1252070343a163]::run_test_in_process::{closure#0}>, core[8f93d80df273fe75]::result::Result<(), alloc[40b2bae28975ac47]::string::String>>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panic.rs:359:14
[INFO] [stdout]   31:     0x5c38234f271a - test[2f1252070343a163]::run_test_in_process
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/test/src/lib.rs:686:27
[INFO] [stdout]   32:     0x5c38234f271a - test[2f1252070343a163]::run_test::{closure#0}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/test/src/lib.rs:607:43
[INFO] [stdout]   33:     0x5c38234ecbe4 - test[2f1252070343a163]::run_test::{closure#1}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/test/src/lib.rs:637:41
[INFO] [stdout]   34:     0x5c38234ecbe4 - std[840933623431fd06]::sys::backtrace::__rust_begin_short_backtrace::<test[2f1252070343a163]::run_test::{closure#1}, ()>
[INFO] [stderr] error: test failed, to rerun pass `-p day-03 --lib`
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/sys/backtrace.rs:166:18
[INFO] [stdout]   35:     0x5c38234f5212 - std[840933623431fd06]::thread::lifecycle::spawn_unchecked::<test[2f1252070343a163]::run_test::{closure#1}, ()>::{closure#1}::{closure#0}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/thread/lifecycle.rs:91:13
[INFO] [stdout]   36:     0x5c38234f5212 - <core[8f93d80df273fe75]::panic::unwind_safe::AssertUnwindSafe<std[840933623431fd06]::thread::lifecycle::spawn_unchecked<test[2f1252070343a163]::run_test::{closure#1}, ()>::{closure#1}::{closure#0}> as core[8f93d80df273fe75]::ops::function::FnOnce<()>>::call_once
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/panic/unwind_safe.rs:274:9
[INFO] [stdout]   37:     0x5c38234f5212 - std[840933623431fd06]::panicking::catch_unwind::do_call::<core[8f93d80df273fe75]::panic::unwind_safe::AssertUnwindSafe<std[840933623431fd06]::thread::lifecycle::spawn_unchecked<test[2f1252070343a163]::run_test::{closure#1}, ()>::{closure#1}::{closure#0}>, ()>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:581:40
[INFO] [stdout]   38:     0x5c38234f5212 - std[840933623431fd06]::panicking::catch_unwind::<(), core[8f93d80df273fe75]::panic::unwind_safe::AssertUnwindSafe<std[840933623431fd06]::thread::lifecycle::spawn_unchecked<test[2f1252070343a163]::run_test::{closure#1}, ()>::{closure#1}::{closure#0}>>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panicking.rs:544:19
[INFO] [stdout]   39:     0x5c38234f5212 - std[840933623431fd06]::panic::catch_unwind::<core[8f93d80df273fe75]::panic::unwind_safe::AssertUnwindSafe<std[840933623431fd06]::thread::lifecycle::spawn_unchecked<test[2f1252070343a163]::run_test::{closure#1}, ()>::{closure#1}::{closure#0}>, ()>
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/panic.rs:359:14
[INFO] [stdout]   40:     0x5c38234f5212 - std[840933623431fd06]::thread::lifecycle::spawn_unchecked::<test[2f1252070343a163]::run_test::{closure#1}, ()>::{closure#1}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/thread/lifecycle.rs:89:26
[INFO] [stdout]   41:     0x5c38234f5212 - <std[840933623431fd06]::thread::lifecycle::spawn_unchecked<test[2f1252070343a163]::run_test::{closure#1}, ()>::{closure#1} as core[8f93d80df273fe75]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   42:     0x5c38237d2a5f - <alloc[40b2bae28975ac47]::boxed::Box<dyn core[8f93d80df273fe75]::ops::function::FnOnce<(), Output = ()> + core[8f93d80df273fe75]::marker::Send> as core[8f93d80df273fe75]::ops::function::FnOnce<()>>::call_once
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/alloc/src/boxed.rs:2206:9
[INFO] [stdout]   43:     0x5c38237d2a5f - <std[840933623431fd06]::sys::thread::unix::Thread>::new::thread_start
[INFO] [stdout]                                at /rustc/bd7d74411512a3dd3b35d2f699c51dd2557c7e7e/library/std/src/sys/thread/unix.rs:119:17
[INFO] [stdout]   44:     0x7912da673aa4 - <unknown>
[INFO] [stdout]   45:     0x7912da700a64 - 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.04s
[INFO] [stdout] 
[INFO] running `Command { std: "docker" "inspect" "8c6d0336002b291c86871fae32e874425b55de19e217df27b518aeff733463ae", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "8c6d0336002b291c86871fae32e874425b55de19e217df27b518aeff733463ae", kill_on_drop: false }`
[INFO] [stdout] 8c6d0336002b291c86871fae32e874425b55de19e217df27b518aeff733463ae
