[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] c63f3ad0ad1289db591e499c0f6c542bbdfcb3ce [INFO] testing Siddid-Soni/advent-of-code-2024 against master#9e136a30a965bf4e63f03095c57df7257bf96fd6 for pr-134530 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024" "/workspace/builds/worker-5-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-5-tc1/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/Siddid-Soni/advent-of-code-2024 on toolchain 9e136a30a965bf4e63f03095c57df7257bf96fd6 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9e136a30a965bf4e63f03095c57df7257bf96fd6" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking git repo https://github.com/Siddid-Soni/advent-of-code-2024 [INFO] finished tweaking git repo https://github.com/Siddid-Soni/advent-of-code-2024 [INFO] tweaked toml for git repo https://github.com/Siddid-Soni/advent-of-code-2024 written to /workspace/builds/worker-5-tc1/source/Cargo.toml [INFO] crate git repo https://github.com/Siddid-Soni/advent-of-code-2024 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9e136a30a965bf4e63f03095c57df7257bf96fd6" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded code-timing-macros v0.0.5 [INFO] [stderr] Downloaded cached v0.54.0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+9e136a30a965bf4e63f03095c57df7257bf96fd6" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 9790280de5707da3f7796877721bfb6c0fcc2a0708f173f605e1c0a2717dd641 [INFO] running `Command { std: "docker" "start" "-a" "9790280de5707da3f7796877721bfb6c0fcc2a0708f173f605e1c0a2717dd641", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "9790280de5707da3f7796877721bfb6c0fcc2a0708f173f605e1c0a2717dd641", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "9790280de5707da3f7796877721bfb6c0fcc2a0708f173f605e1c0a2717dd641", kill_on_drop: false }` [INFO] [stdout] 9790280de5707da3f7796877721bfb6c0fcc2a0708f173f605e1c0a2717dd641 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+9e136a30a965bf4e63f03095c57df7257bf96fd6" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] bd8b95402dff8ff5e588a33749b3914d14081769ea4ef65dedc95cc3849ddc27 [INFO] running `Command { std: "docker" "start" "-a" "bd8b95402dff8ff5e588a33749b3914d14081769ea4ef65dedc95cc3849ddc27", kill_on_drop: false }` [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)` has the same output filename as the bin target `part1` in package `day-01 v0.1.0 (/opt/rustwide/workdir/day-01)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)` has the same output filename as the bin target `part1` in package `day-01 v0.1.0 (/opt/rustwide/workdir/day-01)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)` has the same output filename as the bin target `part2` in package `day-01 v0.1.0 (/opt/rustwide/workdir/day-01)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)` has the same output filename as the bin target `part2` in package `day-01 v0.1.0 (/opt/rustwide/workdir/day-01)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)` has the same output filename as the bin target `part1` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)` has the same output filename as the bin target `part1` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)` has the same output filename as the bin target `part2` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)` has the same output filename as the bin target `part2` in package `day-02 v0.1.0 (/opt/rustwide/workdir/day-02)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)` has the same output filename as the bin target `part1` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)` has the same output filename as the bin target `part1` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)` has the same output filename as the bin target `part2` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)` has the same output filename as the bin target `part2` in package `day-03 v0.1.0 (/opt/rustwide/workdir/day-03)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)` has the same output filename as the bin target `part1` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)` has the same output filename as the bin target `part1` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)` has the same output filename as the bin target `part2` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)` has the same output filename as the bin target `part2` in package `day-04 v0.1.0 (/opt/rustwide/workdir/day-04)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)` has the same output filename as the bin target `part1` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)` has the same output filename as the bin target `part1` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)` has the same output filename as the bin target `part2` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)` has the same output filename as the bin target `part2` in package `day-05 v0.1.0 (/opt/rustwide/workdir/day-05)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)` has the same output filename as the bin target `part1` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)` has the same output filename as the bin target `part1` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)` has the same output filename as the bin target `part2` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)` has the same output filename as the bin target `part2` in package `day-06 v0.1.0 (/opt/rustwide/workdir/day-06)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)` has the same output filename as the bin target `part1` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)` has the same output filename as the bin target `part1` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)` has the same output filename as the bin target `part2` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)` has the same output filename as the bin target `part2` in package `day-07 v0.1.0 (/opt/rustwide/workdir/day-07)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)` has the same output filename as the bin target `part1` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)` has the same output filename as the bin target `part1` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)` has the same output filename as the bin target `part2` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)` has the same output filename as the bin target `part2` in package `day-08 v0.1.0 (/opt/rustwide/workdir/day-08)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)` has the same output filename as the bin target `part1` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)` has the same output filename as the bin target `part1` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)` has the same output filename as the bin target `part2` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)` has the same output filename as the bin target `part2` in package `day-09 v0.1.0 (/opt/rustwide/workdir/day-09)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)` has the same output filename as the bin target `part1` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)` has the same output filename as the bin target `part1` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)` has the same output filename as the bin target `part2` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)` has the same output filename as the bin target `part2` in package `day-10 v0.1.0 (/opt/rustwide/workdir/day-10)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)` has the same output filename as the bin target `part1` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)` has the same output filename as the bin target `part1` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)` has the same output filename as the bin target `part2` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)` has the same output filename as the bin target `part2` in package `day-11 v0.1.0 (/opt/rustwide/workdir/day-11)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)` has the same output filename as the bin target `part1` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)` has the same output filename as the bin target `part1` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)` has the same output filename as the bin target `part2` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)` has the same output filename as the bin target `part2` in package `day-12 v0.1.0 (/opt/rustwide/workdir/day-12)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)` has the same output filename as the bin target `part1` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)` has the same output filename as the bin target `part1` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)` has the same output filename as the bin target `part2` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)` has the same output filename as the bin target `part2` in package `day-13 v0.1.0 (/opt/rustwide/workdir/day-13)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)` has the same output filename as the bin target `part1` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)` has the same output filename as the bin target `part1` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)` has the same output filename as the bin target `part2` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)` has the same output filename as the bin target `part2` in package `day-14 v0.1.0 (/opt/rustwide/workdir/day-14)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)` has the same output filename as the bin target `part1` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)` has the same output filename as the bin target `part1` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)` has the same output filename as the bin target `part2` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)` has the same output filename as the bin target `part2` in package `day-16 v0.1.0 (/opt/rustwide/workdir/day-16)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)` has the same output filename as the bin target `part1` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)` has the same output filename as the bin target `part1` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)` has the same output filename as the bin target `part2` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)` has the same output filename as the bin target `part2` in package `day-17 v0.1.0 (/opt/rustwide/workdir/day-17)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)` has the same output filename as the bin target `part1` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part1` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)` has the same output filename as the bin target `part1` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part1.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)` has the same output filename as the bin target `part2` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2 [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] warning: output filename collision. [INFO] [stderr] The bin target `part2` in package `day-19 v0.1.0 (/opt/rustwide/workdir/day-19)` has the same output filename as the bin target `part2` in package `day-18 v0.1.0 (/opt/rustwide/workdir/day-18)`. [INFO] [stderr] Colliding filename is: /opt/rustwide/target/debug/part2.dwp [INFO] [stderr] The targets should have unique names. [INFO] [stderr] Consider changing their names to be unique or compiling them separately. [INFO] [stderr] This may become a hard error in the future; see . [INFO] [stderr] Compiling proc-macro2 v1.0.92 [INFO] [stderr] Compiling unicode-ident v1.0.14 [INFO] [stderr] Compiling memchr v2.7.4 [INFO] [stderr] Compiling regex-syntax v0.8.5 [INFO] [stderr] Compiling strsim v0.11.1 [INFO] [stderr] Compiling ident_case v1.0.1 [INFO] [stderr] Compiling fnv v1.0.7 [INFO] [stderr] Compiling version_check v0.9.5 [INFO] [stderr] Compiling zerocopy v0.7.35 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling once_cell v1.20.2 [INFO] [stderr] Compiling cfg-if v1.0.0 [INFO] [stderr] Compiling allocator-api2 v0.2.21 [INFO] [stderr] Compiling cached_proc_macro_types v0.1.1 [INFO] [stderr] Compiling web-time v1.1.0 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Compiling aho-corasick v1.1.3 [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-automata v0.4.9 [INFO] [stderr] Compiling darling_core v0.20.10 [INFO] [stderr] Compiling regex v1.11.1 [INFO] [stderr] Compiling code-timing-macros v0.0.5 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08) [INFO] [stderr] Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02) [INFO] [stderr] Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12) [INFO] [stderr] Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13) [INFO] [stderr] Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18) [INFO] [stderr] Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05) [INFO] [stderr] Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14) [INFO] [stderr] Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01) [INFO] [stderr] Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04) [INFO] [stderr] Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10) [INFO] [stderr] Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17) [INFO] [stderr] Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09) [INFO] [stderr] Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19) [INFO] [stderr] Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03) [INFO] [stderr] Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06) [INFO] [stderr] Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07) [INFO] [stderr] Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16) [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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling darling_macro v0.20.10 [INFO] [stderr] Compiling darling v0.20.10 [INFO] [stderr] Compiling cached_proc_macro v0.23.0 [INFO] [stderr] Compiling cached v0.54.0 [INFO] [stderr] Compiling day-11 v0.1.0 (/opt/rustwide/workdir/day-11) [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-11/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-11/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: 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 21.90s [INFO] running `Command { std: "docker" "inspect" "bd8b95402dff8ff5e588a33749b3914d14081769ea4ef65dedc95cc3849ddc27", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "bd8b95402dff8ff5e588a33749b3914d14081769ea4ef65dedc95cc3849ddc27", kill_on_drop: false }` [INFO] [stdout] bd8b95402dff8ff5e588a33749b3914d14081769ea4ef65dedc95cc3849ddc27 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+9e136a30a965bf4e63f03095c57df7257bf96fd6" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] c598137ecac9a3603e4bb46e1362af01c429af26e4d395e8a9c498222f88b05f [INFO] running `Command { std: "docker" "start" "-a" "c598137ecac9a3603e4bb46e1362af01c429af26e4d395e8a9c498222f88b05f", kill_on_drop: false }` [INFO] [stderr] Compiling rustix v0.38.41 [INFO] [stderr] Compiling linux-raw-sys v0.4.14 [INFO] [stderr] Compiling bitflags v2.6.0 [INFO] [stderr] Compiling libc v0.2.167 [INFO] [stderr] Compiling anstyle v1.0.10 [INFO] [stderr] Compiling clap_lex v0.7.4 [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-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-03 v0.1.0 (/opt/rustwide/workdir/day-03) [INFO] [stderr] Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04) [INFO] [stderr] Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06) [INFO] [stderr] Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13) [INFO] [stderr] Compiling day-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-19 v0.1.0 (/opt/rustwide/workdir/day-19) [INFO] [stderr] Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18) [INFO] [stderr] Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09) [INFO] [stderr] Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16) [INFO] [stderr] Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14) [INFO] [stderr] Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05) [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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08) [INFO] [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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02) [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: 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-10 v0.1.0 (/opt/rustwide/workdir/day-10) [INFO] [stderr] Compiling day-11 v0.1.0 (/opt/rustwide/workdir/day-11) [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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly 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 for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: 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 9.92s [INFO] running `Command { std: "docker" "inspect" "c598137ecac9a3603e4bb46e1362af01c429af26e4d395e8a9c498222f88b05f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c598137ecac9a3603e4bb46e1362af01c429af26e4d395e8a9c498222f88b05f", kill_on_drop: false }` [INFO] [stdout] c598137ecac9a3603e4bb46e1362af01c429af26e4d395e8a9c498222f88b05f [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+9e136a30a965bf4e63f03095c57df7257bf96fd6" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] 2fba9dcdaf975fe0eb06f5a79a681b7a401d77aa3eb5c45d463094d7d3f09139 [INFO] running `Command { std: "docker" "start" "-a" "2fba9dcdaf975fe0eb06f5a79a681b7a401d77aa3eb5c45d463094d7d3f09139", kill_on_drop: false }` [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 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 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 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 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-09` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-01` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: `day-04` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-04` (bin "part1" test) generated 1 warning [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 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 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 for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `tracing` [INFO] [stderr] --> day-12/src/bin/part2.rs:5:18 [INFO] [stderr] | [INFO] [stderr] 5 | let result = time_snippet!(process("day-12/input1.txt")); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stderr] = note: see 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 for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `day-02` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-01` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-07` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: `day-12` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-09` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: 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 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 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 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 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 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 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 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 for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `tracing` [INFO] [stderr] --> day-06/src/bin/part1.rs:5:18 [INFO] [stderr] | [INFO] [stderr] 5 | let result = time_snippet!(process("day-06/input1.txt")); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stderr] = note: see 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 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-13` (bin "part2" 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-14` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-03` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-03` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: `day-05` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-06` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-06` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: `day-02` (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 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 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 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 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 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] [stdout] [INFO] [stderr] | [INFO] [stdout] running 2 tests [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 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-08` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-19` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-10` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: `day-10` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-18` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: unexpected `cfg` condition value: `tracing` [INFO] [stderr] --> day-11/src/bin/part2.rs:5:18 [INFO] [stderr] | [INFO] [stderr] 5 | let result = time_snippet!(process("day-11/input1.txt")); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stderr] = note: see 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 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 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 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 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] [stdout] test part1::tests::test_process ... ok [INFO] [stderr] | [INFO] [stdout] test part2::tests::test_process ... ok [INFO] [stderr] 5 | let result = time_snippet!(process("day-08/input1.txt")); [INFO] [stdout] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stderr] | [INFO] [stdout] [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 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 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 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 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-16` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: `day-17` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-18` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-08` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: `day-07` (bin "part2" test) generated 1 warning [INFO] [stderr] warning: `day-05` (bin "part1" test) generated 1 warning [INFO] [stderr] warning: `day-19` (bin "part1" 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 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 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-16` (bin "part2" test) generated 1 warning [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.10s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_01-c8d1efdf44e1b0d7) [INFO] [stderr] Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/deps/part1-6f6fe6fccc9424a5) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/deps/part2-2c12b31dda0b2d17) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_02-fd54d4eb8f2705fd) [INFO] [stdout] [INFO] [stdout] running 2 tests [INFO] [stdout] test part2::tests::test_process ... ok [INFO] [stdout] test part1::tests::test_process ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests src/bin/part1.rs (/opt/rustwide/target/debug/deps/part1-7e4a5c1827a0b204) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests src/bin/part2.rs (/opt/rustwide/target/debug/deps/part2-890351441099740d) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/day_03-4fb9a3425a550036) [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 2 tests [INFO] [stdout] test part1::tests::test_process ... ok [INFO] [stdout] test part2::tests::test_process ... FAILED [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] [INFO] [stdout] ---- part2::tests::test_process stdout ---- [INFO] [stdout] thread 'part2::tests::test_process' panicked at day-03/src/part2.rs:32:9: [INFO] [stdout] assertion `left == right` failed [INFO] [stdout] left: 42 [INFO] [stdout] right: 48 [INFO] [stdout] stack backtrace: [INFO] [stdout] 0: 0x57af86fcb1ca - std::backtrace_rs::backtrace::libunwind::trace::h45f575fdcec9cdc1 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5 [INFO] [stdout] 1: 0x57af86fcb1ca - std::backtrace_rs::backtrace::trace_unsynchronized::heed7aaaa28209ac3 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5 [INFO] [stdout] 2: 0x57af86fcb1ca - std::sys::backtrace::_print_fmt::h47d1e3547844619c [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/sys/backtrace.rs:66:9 [INFO] [stdout] 3: 0x57af86fcb1ca - ::fmt::h6c37de0361fa7462 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/sys/backtrace.rs:39:26 [INFO] [stdout] 4: 0x57af86ff2753 - core::fmt::rt::Argument::fmt::h6606d9b5304941e1 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/fmt/rt.rs:177:76 [INFO] [stdout] 5: 0x57af86ff2753 - core::fmt::write::hf77fe0583268bf67 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/fmt/mod.rs:1437:21 [INFO] [stdout] 6: 0x57af86fc7ec3 - std::io::Write::write_fmt::h672ff980e46892ac [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/io/mod.rs:1887:15 [INFO] [stdout] 7: 0x57af86fcb012 - std::sys::backtrace::BacktraceLock::print::hce84519ec0e7588e [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/sys/backtrace.rs:42:9 [INFO] [stdout] 8: 0x57af86fcc64e - std::panicking::default_hook::{{closure}}::h6e0433c33d1ed12b [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:284:22 [INFO] [stdout] 9: 0x57af86fcc457 - std::panicking::default_hook::h19d4e9e8d7fba9e2 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:308:9 [INFO] [stdout] 10: 0x57af86d19c88 - as core::ops::function::Fn>::call::hd2aa5731f018e269 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/alloc/src/boxed.rs:1984:9 [INFO] [stdout] 11: 0x57af86d19c88 - test::test_main::{{closure}}::h1ae6fb8f80aa49b6 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/test/src/lib.rs:134:21 [INFO] [stdout] 12: 0x57af86fcce68 - as core::ops::function::Fn>::call::h4f2af756974b90d5 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/alloc/src/boxed.rs:1984:9 [INFO] [stdout] 13: 0x57af86fcce68 - std::panicking::rust_panic_with_hook::hd21771b96ea64164 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:825:13 [INFO] [stdout] 14: 0x57af86fccb1a - std::panicking::begin_panic_handler::{{closure}}::h2e177f984fc72cbb [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:690:13 [INFO] [stdout] 15: 0x57af86fcb6a9 - std::sys::backtrace::__rust_end_short_backtrace::ha7f0445003f40b38 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/sys/backtrace.rs:168:18 [INFO] [stdout] 16: 0x57af86fcc7ad - rust_begin_unwind [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:681:5 [INFO] [stdout] 17: 0x57af86ff0de0 - core::panicking::panic_fmt::h85741df7bc4071b6 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/panicking.rs:75:14 [INFO] [stdout] 18: 0x57af86ff11d2 - core::panicking::assert_failed_inner::h889a6bf80d9117a5 [INFO] [stdout] 19: 0x57af86faae2c - core::panicking::assert_failed::he8c2744964b4688f [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/panicking.rs:364:5 [INFO] [stdout] 20: 0x57af86cdf6e9 - day_03::part2::tests::test_process::h5073a4aa31fac2a8 [INFO] [stdout] at /opt/rustwide/workdir/day-03/src/part2.rs:32:9 [INFO] [stdout] 21: 0x57af86cdf667 - day_03::part2::tests::test_process::{{closure}}::h2a3e00e9fbe13e64 [INFO] [stdout] at /opt/rustwide/workdir/day-03/src/part2.rs:31:22 [INFO] [stdout] 22: 0x57af86cda666 - core::ops::function::FnOnce::call_once::hfed9feebd7632771 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 23: 0x57af86d1e8cb - core::ops::function::FnOnce::call_once::hc1e06e2a5640370a [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 24: 0x57af86d1e8cb - test::__rust_begin_short_backtrace::heb5aa654e2797f5b [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/test/src/lib.rs:632:18 [INFO] [stdout] 25: 0x57af86d1e1d9 - test::run_test_in_process::{{closure}}::h1329474a96646ad1 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/test/src/lib.rs:655:60 [INFO] [stdout] 26: 0x57af86d1e1d9 - as core::ops::function::FnOnce<()>>::call_once::hc87a7a8694e6d844 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/panic/unwind_safe.rs:272:9 [INFO] [stdout] 27: 0x57af86d1e1d9 - std::panicking::try::do_call::h3b8456af8bacf88f [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:573:40 [INFO] [stdout] 28: 0x57af86d1e1d9 - std::panicking::try::hc177f95c6592cea1 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:536:19 [INFO] [stdout] 29: 0x57af86d1e1d9 - std::panic::catch_unwind::h847b2adf17f7da7a [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panic.rs:358:14 [INFO] [stdout] 30: 0x57af86d1e1d9 - test::run_test_in_process::h824f7775d92af51e [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/test/src/lib.rs:655:27 [INFO] [stdout] 31: 0x57af86d1e1d9 - test::run_test::{{closure}}::hdfaf20d18f7af8f6 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/test/src/lib.rs:576:43 [INFO] [stdout] 32: 0x57af86ce0f7a - test::run_test::{{closure}}::he83661a0a1c97403 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/test/src/lib.rs:606:41 [INFO] [stdout] 33: 0x57af86ce0f7a - std::sys::backtrace::__rust_begin_short_backtrace::hd3a78fd401685e9b [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/sys/backtrace.rs:152:18 [INFO] [stdout] 34: 0x57af86ce49b6 - std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::h78d6a457dee8dc60 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/thread/mod.rs:561:17 [INFO] [stdout] 35: 0x57af86ce49b6 - as core::ops::function::FnOnce<()>>::call_once::hc4069b3cc6600bde [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/panic/unwind_safe.rs:272:9 [INFO] [stdout] 36: 0x57af86ce49b6 - std::panicking::try::do_call::h0dde49ad0af85fa8 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:573:40 [INFO] [stdout] 37: 0x57af86ce49b6 - std::panicking::try::h918d0d3a7e94727d [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panicking.rs:536:19 [INFO] [stdout] 38: 0x57af86ce49b6 - std::panic::catch_unwind::h7016984cdcdd8b9e [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/panic.rs:358:14 [INFO] [stdout] 39: 0x57af86ce49b6 - std::thread::Builder::spawn_unchecked_::{{closure}}::h2766f51195a4a65d [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/thread/mod.rs:559:30 [INFO] [stdout] 40: 0x57af86ce49b6 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hbd6e39e4ea63a011 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 41: 0x57af86fd0d3b - as core::ops::function::FnOnce>::call_once::h34bec2a4cdedc102 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/alloc/src/boxed.rs:1970:9 [INFO] [stdout] 42: 0x57af86fd0d3b - as core::ops::function::FnOnce>::call_once::ha62c0d1861fdf293 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/alloc/src/boxed.rs:1970:9 [INFO] [stdout] 43: 0x57af86fd0d3b - std::sys::pal::unix::thread::Thread::new::thread_start::h71fe57097907b3f8 [INFO] [stdout] at /rustc/9e136a30a965bf4e63f03095c57df7257bf96fd6/library/std/src/sys/pal/unix/thread.rs:105:17 [INFO] [stdout] 44: 0x779cdc003ac3 - [INFO] [stdout] 45: 0x779cdc094a04 - clone [INFO] [stdout] 46: 0x0 - [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] part2::tests::test_process [INFO] [stdout] [INFO] [stdout] test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.03s [INFO] [stdout] [INFO] [stderr] error: test failed, to rerun pass `-p day-03 --lib` [INFO] running `Command { std: "docker" "inspect" "2fba9dcdaf975fe0eb06f5a79a681b7a401d77aa3eb5c45d463094d7d3f09139", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2fba9dcdaf975fe0eb06f5a79a681b7a401d77aa3eb5c45d463094d7d3f09139", kill_on_drop: false }` [INFO] [stdout] 2fba9dcdaf975fe0eb06f5a79a681b7a401d77aa3eb5c45d463094d7d3f09139