[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 try#ed7f3d77595b4831fdf085f2529aa13b5b51ff7d 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-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-5-tc2/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/Siddid-Soni/advent-of-code-2024 on toolchain ed7f3d77595b4831fdf085f2529aa13b5b51ff7d [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ed7f3d77595b4831fdf085f2529aa13b5b51ff7d" "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-tc2/source/Cargo.toml [INFO] crate git repo https://github.com/Siddid-Soni/advent-of-code-2024 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ed7f3d77595b4831fdf085f2529aa13b5b51ff7d" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+ed7f3d77595b4831fdf085f2529aa13b5b51ff7d" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] da1ca7dcb976db69c7ed71e8585751a713f3bd8c3f6bf0f64e91c9be24424876 [INFO] running `Command { std: "docker" "start" "-a" "da1ca7dcb976db69c7ed71e8585751a713f3bd8c3f6bf0f64e91c9be24424876", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "da1ca7dcb976db69c7ed71e8585751a713f3bd8c3f6bf0f64e91c9be24424876", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "da1ca7dcb976db69c7ed71e8585751a713f3bd8c3f6bf0f64e91c9be24424876", kill_on_drop: false }` [INFO] [stdout] da1ca7dcb976db69c7ed71e8585751a713f3bd8c3f6bf0f64e91c9be24424876 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+ed7f3d77595b4831fdf085f2529aa13b5b51ff7d" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 2bcae350246de863cef97275441e7a3bf1025a3390a2bebfcc1aa5783f754344 [INFO] running `Command { std: "docker" "start" "-a" "2bcae350246de863cef97275441e7a3bf1025a3390a2bebfcc1aa5783f754344", 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 fnv v1.0.7 [INFO] [stderr] Compiling strsim v0.11.1 [INFO] [stderr] Compiling version_check v0.9.5 [INFO] [stderr] Compiling ident_case v1.0.1 [INFO] [stderr] Compiling cfg-if v1.0.0 [INFO] [stderr] Compiling zerocopy v0.7.35 [INFO] [stderr] Compiling once_cell v1.20.2 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling allocator-api2 v0.2.21 [INFO] [stderr] Compiling web-time v1.1.0 [INFO] [stderr] Compiling cached_proc_macro_types v0.1.1 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Compiling hashbrown v0.14.5 [INFO] [stderr] Compiling quote v1.0.37 [INFO] [stderr] Compiling aho-corasick v1.1.3 [INFO] [stderr] Compiling syn v2.0.90 [INFO] [stderr] Compiling regex-automata v0.4.9 [INFO] [stderr] Compiling darling_core v0.20.10 [INFO] [stderr] Compiling code-timing-macros v0.0.5 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling regex v1.11.1 [INFO] [stderr] Compiling day-06 v0.1.0 (/opt/rustwide/workdir/day-06) [INFO] [stderr] Compiling day-09 v0.1.0 (/opt/rustwide/workdir/day-09) [INFO] [stderr] Compiling day-18 v0.1.0 (/opt/rustwide/workdir/day-18) [INFO] [stderr] Compiling day-12 v0.1.0 (/opt/rustwide/workdir/day-12) [INFO] [stderr] Compiling day-08 v0.1.0 (/opt/rustwide/workdir/day-08) [INFO] [stderr] Compiling day-04 v0.1.0 (/opt/rustwide/workdir/day-04) [INFO] [stderr] Compiling day-19 v0.1.0 (/opt/rustwide/workdir/day-19) [INFO] [stderr] Compiling day-05 v0.1.0 (/opt/rustwide/workdir/day-05) [INFO] [stderr] Compiling day-02 v0.1.0 (/opt/rustwide/workdir/day-02) [INFO] [stderr] Compiling day-01 v0.1.0 (/opt/rustwide/workdir/day-01) [INFO] [stderr] Compiling day-07 v0.1.0 (/opt/rustwide/workdir/day-07) [INFO] [stderr] Compiling day-17 v0.1.0 (/opt/rustwide/workdir/day-17) [INFO] [stderr] Compiling day-16 v0.1.0 (/opt/rustwide/workdir/day-16) [INFO] [stderr] Compiling day-10 v0.1.0 (/opt/rustwide/workdir/day-10) [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-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-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-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-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-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-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-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-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/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] [stderr] Compiling day-14 v0.1.0 (/opt/rustwide/workdir/day-14) [INFO] [stderr] Compiling day-03 v0.1.0 (/opt/rustwide/workdir/day-03) [INFO] [stderr] Compiling day-13 v0.1.0 (/opt/rustwide/workdir/day-13) [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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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] [stderr] Compiling darling_macro v0.20.10 [INFO] [stderr] Compiling darling v0.20.10 [INFO] [stderr] Compiling cached_proc_macro v0.23.0 [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-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-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-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-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-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] [stderr] error: failed to remove file `/opt/rustwide/target/debug/part1` [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] No such file or directory (os error 2) [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] running `Command { std: "docker" "inspect" "2bcae350246de863cef97275441e7a3bf1025a3390a2bebfcc1aa5783f754344", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2bcae350246de863cef97275441e7a3bf1025a3390a2bebfcc1aa5783f754344", kill_on_drop: false }` [INFO] [stdout] 2bcae350246de863cef97275441e7a3bf1025a3390a2bebfcc1aa5783f754344