[INFO] cloning repository https://github.com/Grub4K/bm.rs [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/Grub4K/bm.rs" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FGrub4K%2Fbm.rs", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FGrub4K%2Fbm.rs'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] a0c984d29ff25b044bfd481f8e414b7af74be5da [INFO] checking Grub4K/bm.rs against try#44f3504e96c944ae54fc72b5f5008f53f7eda001 for pr-136776 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FGrub4K%2Fbm.rs" "/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/Grub4K/bm.rs on toolchain 44f3504e96c944ae54fc72b5f5008f53f7eda001 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+44f3504e96c944ae54fc72b5f5008f53f7eda001" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking git repo https://github.com/Grub4K/bm.rs [INFO] finished tweaking git repo https://github.com/Grub4K/bm.rs [INFO] tweaked toml for git repo https://github.com/Grub4K/bm.rs written to /workspace/builds/worker-5-tc2/source/Cargo.toml [INFO] crate git repo https://github.com/Grub4K/bm.rs 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" "+44f3504e96c944ae54fc72b5f5008f53f7eda001" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded is_ci v1.1.1 [INFO] [stderr] Downloaded owo-colors v4.0.0 [INFO] [stderr] Downloaded anstream v0.6.12 [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:3959728d45483eb673ba100a951a6b9f5012970368db2a9e08e0ac9b67c8a5ad" "/opt/rustwide/cargo-home/bin/cargo" "+44f3504e96c944ae54fc72b5f5008f53f7eda001" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 717832afbb2b8e7799640a820319f991ee80ebf607a68704ce3039e078970e33 [INFO] running `Command { std: "docker" "start" "-a" "717832afbb2b8e7799640a820319f991ee80ebf607a68704ce3039e078970e33", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "717832afbb2b8e7799640a820319f991ee80ebf607a68704ce3039e078970e33", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "717832afbb2b8e7799640a820319f991ee80ebf607a68704ce3039e078970e33", kill_on_drop: false }` [INFO] [stdout] 717832afbb2b8e7799640a820319f991ee80ebf607a68704ce3039e078970e33 [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:3959728d45483eb673ba100a951a6b9f5012970368db2a9e08e0ac9b67c8a5ad" "/opt/rustwide/cargo-home/bin/cargo" "+44f3504e96c944ae54fc72b5f5008f53f7eda001" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 56c9f658ebbb87d52fb9e366a71f488547df9efcdf117ee58273d5c912498b1e [INFO] running `Command { std: "docker" "start" "-a" "56c9f658ebbb87d52fb9e366a71f488547df9efcdf117ee58273d5c912498b1e", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.78 [INFO] [stderr] Compiling rustix v0.38.30 [INFO] [stderr] Compiling unicode-ident v1.0.12 [INFO] [stderr] Checking linux-raw-sys v0.4.13 [INFO] [stderr] Checking bitflags v2.4.2 [INFO] [stderr] Checking utf8parse v0.2.1 [INFO] [stderr] Checking anstyle v1.0.6 [INFO] [stderr] Checking anstyle-query v1.0.2 [INFO] [stderr] Checking colorchoice v1.0.0 [INFO] [stderr] Checking anstyle-parse v0.2.3 [INFO] [stderr] Checking strsim v0.11.0 [INFO] [stderr] Checking option-ext v0.2.0 [INFO] [stderr] Checking once_cell v1.19.0 [INFO] [stderr] Compiling heck v0.4.1 [INFO] [stderr] Checking is_ci v1.1.1 [INFO] [stderr] Checking anstream v0.6.12 [INFO] [stderr] Checking clap_lex v0.7.0 [INFO] [stderr] Checking dirs-sys v0.4.1 [INFO] [stderr] Checking path-dedot v3.1.1 [INFO] [stderr] Compiling indoc v2.0.4 [INFO] [stderr] Checking path-absolutize v3.1.1 [INFO] [stderr] Checking dirs v5.0.1 [INFO] [stderr] Checking glob v0.3.1 [INFO] [stderr] Checking clap_builder v4.5.1 [INFO] [stderr] Compiling quote v1.0.35 [INFO] [stderr] Compiling syn v2.0.50 [INFO] [stderr] Checking is-terminal v0.4.10 [INFO] [stderr] Checking supports-color v2.1.0 [INFO] [stderr] Checking owo-colors v4.0.0 [INFO] [stderr] Compiling clap_derive v4.5.0 [INFO] [stderr] Checking clap v4.5.1 [INFO] [stderr] Checking bm v0.1.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_cd.rs:11:13 [INFO] [stdout] | [INFO] [stdout] 11 | utils::error!("No matching bookmark found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [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 `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_cd.rs:15:13 [INFO] [stdout] | [INFO] [stdout] 15 | utils::error!("More than one matching bookmark found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_conf.rs:17:13 [INFO] [stdout] | [INFO] [stdout] 17 | utils::error!("could not spawn editor process: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_del.rs:7:9 [INFO] [stdout] | [INFO] [stdout] 7 | utils::error!("invalid name for a bookmark: {bookmark:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_del.rs:18:13 [INFO] [stdout] | [INFO] [stdout] 18 | utils::error!("could not find bookmark: {bookmark}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_ls.rs:32:13 [INFO] [stdout] | [INFO] [stdout] 32 | utils::error!("failed to write to stdout: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_set.rs:13:9 [INFO] [stdout] | [INFO] [stdout] 13 | utils::error!("invalid name for a bookmark: {bookmark:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_set.rs:18:13 [INFO] [stdout] | [INFO] [stdout] 18 | utils::error!("could not determine current directory: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_set.rs:26:9 [INFO] [stdout] | [INFO] [stdout] 26 | utils::error!("could not set path: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_set.rs:43:13 [INFO] [stdout] | [INFO] [stdout] 43 | utils::error!("key {bookmark:?} already exists"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:33:17 [INFO] [stdout] | [INFO] [stdout] 33 | error!("could not resolve system config dir"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:42:13 [INFO] [stdout] | [INFO] [stdout] 42 | error!("could not create config dir: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:51:13 [INFO] [stdout] | [INFO] [stdout] 51 | error!("could not create config file: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:66:13 [INFO] [stdout] | [INFO] [stdout] 66 | error!("could not create glob: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:75:9 [INFO] [stdout] | [INFO] [stdout] 75 | error!("could not open config file for reading: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:81:13 [INFO] [stdout] | [INFO] [stdout] 81 | error!("could not read line: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | error!("could not parse config: invalid key in line {index}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:94:13 [INFO] [stdout] | [INFO] [stdout] 94 | error!("could not parse config: no value in line {index}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:129:9 [INFO] [stdout] | [INFO] [stdout] 129 | error!("could not open config file for writing: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:142:17 [INFO] [stdout] | [INFO] [stdout] 142 | error!("could not write line: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_cd.rs:11:13 [INFO] [stdout] | [INFO] [stdout] 11 | utils::error!("No matching bookmark found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [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 `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_cd.rs:15:13 [INFO] [stdout] | [INFO] [stdout] 15 | utils::error!("More than one matching bookmark found"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_conf.rs:17:13 [INFO] [stdout] | [INFO] [stdout] 17 | utils::error!("could not spawn editor process: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_del.rs:7:9 [INFO] [stdout] | [INFO] [stdout] 7 | utils::error!("invalid name for a bookmark: {bookmark:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_del.rs:18:13 [INFO] [stdout] | [INFO] [stdout] 18 | utils::error!("could not find bookmark: {bookmark}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_ls.rs:32:13 [INFO] [stdout] | [INFO] [stdout] 32 | utils::error!("failed to write to stdout: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_set.rs:13:9 [INFO] [stdout] | [INFO] [stdout] 13 | utils::error!("invalid name for a bookmark: {bookmark:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_set.rs:18:13 [INFO] [stdout] | [INFO] [stdout] 18 | utils::error!("could not determine current directory: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_set.rs:26:9 [INFO] [stdout] | [INFO] [stdout] 26 | utils::error!("could not set path: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/action_set.rs:43:13 [INFO] [stdout] | [INFO] [stdout] 43 | utils::error!("key {bookmark:?} already exists"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `utils::error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:33:17 [INFO] [stdout] | [INFO] [stdout] 33 | error!("could not resolve system config dir"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:42:13 [INFO] [stdout] | [INFO] [stdout] 42 | error!("could not create config dir: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:51:13 [INFO] [stdout] | [INFO] [stdout] 51 | error!("could not create config file: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:66:13 [INFO] [stdout] | [INFO] [stdout] 66 | error!("could not create glob: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:75:9 [INFO] [stdout] | [INFO] [stdout] 75 | error!("could not open config file for reading: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:81:13 [INFO] [stdout] | [INFO] [stdout] 81 | error!("could not read line: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | error!("could not parse config: invalid key in line {index}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:94:13 [INFO] [stdout] | [INFO] [stdout] 94 | error!("could not parse config: no value in line {index}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:129:9 [INFO] [stdout] | [INFO] [stdout] 129 | error!("could not open config file for writing: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> src/utils.rs:142:17 [INFO] [stdout] | [INFO] [stdout] 142 | error!("could not write line: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `anstream::eprintln` which comes from the expansion of the macro `error` (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 5.65s [INFO] running `Command { std: "docker" "inspect" "56c9f658ebbb87d52fb9e366a71f488547df9efcdf117ee58273d5c912498b1e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "56c9f658ebbb87d52fb9e366a71f488547df9efcdf117ee58273d5c912498b1e", kill_on_drop: false }` [INFO] [stdout] 56c9f658ebbb87d52fb9e366a71f488547df9efcdf117ee58273d5c912498b1e