[INFO] fetching crate icann-rdap-common 0.0.21... [INFO] testing icann-rdap-common-0.0.21 against beta-2025-02-18 for beta-1.86-1 [INFO] extracting crate icann-rdap-common 0.0.21 into /workspace/builds/worker-6-tc2/source [INFO] validating manifest of crates.io crate icann-rdap-common 0.0.21 on toolchain beta-2025-02-18 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-02-18" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate icann-rdap-common 0.0.21 [INFO] finished tweaking crates.io crate icann-rdap-common 0.0.21 [INFO] tweaked toml for crates.io crate icann-rdap-common 0.0.21 written to /workspace/builds/worker-6-tc2/source/Cargo.toml [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-02-18" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 89 packages to latest compatible versions [INFO] [stderr] Adding buildstructor v0.5.4 (available: v0.6.0) [INFO] [stderr] Adding idna v0.5.0 (available: v1.0.3) [INFO] [stderr] Adding prefix-trie v0.2.5 (available: v0.6.0) [INFO] [stderr] Adding rstest v0.17.0 (available: v0.24.0) [INFO] [stderr] Adding strum v0.24.1 (available: v0.27.1) [INFO] [stderr] Adding strum_macros v0.24.3 (available: v0.27.1) [INFO] [stderr] Adding thiserror v1.0.69 (available: v2.0.11) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-02-18" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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" "+beta-2025-02-18" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 6a3e558a98a66e1ac4cfae813801beb606ff0a9d42857df286a40a3b8565762c [INFO] running `Command { std: "docker" "start" "-a" "6a3e558a98a66e1ac4cfae813801beb606ff0a9d42857df286a40a3b8565762c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "6a3e558a98a66e1ac4cfae813801beb606ff0a9d42857df286a40a3b8565762c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6a3e558a98a66e1ac4cfae813801beb606ff0a9d42857df286a40a3b8565762c", kill_on_drop: false }` [INFO] [stdout] 6a3e558a98a66e1ac4cfae813801beb606ff0a9d42857df286a40a3b8565762c [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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" "+beta-2025-02-18" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 2a03436727971b8ec7715435464ee310c65304e01a336c8d8a76ece33e8eeafe [INFO] running `Command { std: "docker" "start" "-a" "2a03436727971b8ec7715435464ee310c65304e01a336c8d8a76ece33e8eeafe", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.93 [INFO] [stderr] Compiling unicode-ident v1.0.17 [INFO] [stderr] Compiling memchr v2.7.4 [INFO] [stderr] Compiling serde v1.0.218 [INFO] [stderr] Compiling serde_json v1.0.139 [INFO] [stderr] Compiling autocfg v1.4.0 [INFO] [stderr] Compiling regex-syntax v0.8.5 [INFO] [stderr] Compiling schemars v0.8.21 [INFO] [stderr] Compiling itoa v1.0.14 [INFO] [stderr] Compiling ryu v1.0.19 [INFO] [stderr] Compiling dyn-clone v1.0.18 [INFO] [stderr] Compiling rustversion v1.0.19 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling tinyvec_macros v0.1.1 [INFO] [stderr] Compiling lazy_static v1.5.0 [INFO] [stderr] Compiling tinyvec v1.8.1 [INFO] [stderr] Compiling unicode-xid v0.2.6 [INFO] [stderr] Compiling unicode-bidi v0.3.18 [INFO] [stderr] Compiling heck v0.4.1 [INFO] [stderr] Compiling iana-time-zone v0.1.61 [INFO] [stderr] Compiling cidr v0.3.1 [INFO] [stderr] Compiling strum v0.24.1 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling aho-corasick v1.1.3 [INFO] [stderr] Compiling unicode-normalization v0.1.24 [INFO] [stderr] Compiling quote v1.0.38 [INFO] [stderr] Compiling syn v2.0.98 [INFO] [stderr] Compiling const_format_proc_macros v0.2.34 [INFO] [stderr] Compiling idna v0.5.0 [INFO] [stderr] Compiling regex-automata v0.4.9 [INFO] [stderr] Compiling const_format v0.2.34 [INFO] [stderr] Compiling strum_macros v0.24.3 [INFO] [stderr] Compiling regex v1.11.1 [INFO] [stderr] Compiling str_inflector v0.12.0 [INFO] [stderr] Compiling serde_derive_internals v0.29.1 [INFO] [stderr] Compiling serde_derive v1.0.218 [INFO] [stderr] Compiling try_match_inner v0.5.2 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling schemars_derive v0.8.21 [INFO] [stderr] Compiling try_match v0.4.2 [INFO] [stderr] Compiling buildstructor v0.5.4 [INFO] [stderr] Compiling chrono v0.4.39 [INFO] [stderr] Compiling ipnet v2.11.0 [INFO] [stderr] Compiling prefix-trie v0.2.5 [INFO] [stderr] Compiling icann-rdap-common v0.0.21 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:103:17 [INFO] [stdout] | [INFO] [stdout] 103 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [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 attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:219:17 [INFO] [stdout] | [INFO] [stdout] 219 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:239:17 [INFO] [stdout] | [INFO] [stdout] 239 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:258:17 [INFO] [stdout] | [INFO] [stdout] 258 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:302:17 [INFO] [stdout] | [INFO] [stdout] 302 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:333:17 [INFO] [stdout] | [INFO] [stdout] 333 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/httpdata.rs:7:48 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Serialize, Deserialize, Clone, Debug, Builder, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/httpdata.rs:24:1 [INFO] [stdout] | [INFO] [stdout] 24 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/autnum.rs:43:34 [INFO] [stdout] | [INFO] [stdout] 43 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/autnum.rs:70:1 [INFO] [stdout] | [INFO] [stdout] 70 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:12:34 [INFO] [stdout] | [INFO] [stdout] 12 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:24:34 [INFO] [stdout] | [INFO] [stdout] 24 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:37:34 [INFO] [stdout] | [INFO] [stdout] 37 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:60:34 [INFO] [stdout] | [INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:83:34 [INFO] [stdout] | [INFO] [stdout] 83 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:140:34 [INFO] [stdout] | [INFO] [stdout] 140 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:174:1 [INFO] [stdout] | [INFO] [stdout] 174 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/entity.rs:81:34 [INFO] [stdout] | [INFO] [stdout] 81 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/entity.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/error.rs:9:34 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/error.rs:24:1 [INFO] [stdout] | [INFO] [stdout] 24 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/help.rs:8:34 [INFO] [stdout] | [INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/help.rs:14:1 [INFO] [stdout] | [INFO] [stdout] 14 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:12:34 [INFO] [stdout] | [INFO] [stdout] 12 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:21:1 [INFO] [stdout] | [INFO] [stdout] 21 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:94:34 [INFO] [stdout] | [INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:115:1 [INFO] [stdout] | [INFO] [stdout] 115 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:149:34 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:187:1 [INFO] [stdout] | [INFO] [stdout] 187 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/redacted.rs:52:10 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Builder, Serialize, Deserialize, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:7:34 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:28:34 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:49:34 [INFO] [stdout] | [INFO] [stdout] 49 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:58:1 [INFO] [stdout] | [INFO] [stdout] 58 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:189:1 [INFO] [stdout] | [INFO] [stdout] 189 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:290:1 [INFO] [stdout] | [INFO] [stdout] 290 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:361:1 [INFO] [stdout] | [INFO] [stdout] 361 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:436:1 [INFO] [stdout] | [INFO] [stdout] 436 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:448:34 [INFO] [stdout] | [INFO] [stdout] 448 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:458:1 [INFO] [stdout] | [INFO] [stdout] 458 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:481:34 [INFO] [stdout] | [INFO] [stdout] 481 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:512:1 [INFO] [stdout] | [INFO] [stdout] 512 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (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 28.27s [INFO] running `Command { std: "docker" "inspect" "2a03436727971b8ec7715435464ee310c65304e01a336c8d8a76ece33e8eeafe", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2a03436727971b8ec7715435464ee310c65304e01a336c8d8a76ece33e8eeafe", kill_on_drop: false }` [INFO] [stdout] 2a03436727971b8ec7715435464ee310c65304e01a336c8d8a76ece33e8eeafe [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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" "+beta-2025-02-18" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] d5463c11f2c1475ce58a73d283e8214512b91cc8e40ae76cd64e99512b920df8 [INFO] running `Command { std: "docker" "start" "-a" "d5463c11f2c1475ce58a73d283e8214512b91cc8e40ae76cd64e99512b920df8", kill_on_drop: false }` [INFO] [stderr] Compiling memchr v2.7.4 [INFO] [stderr] Compiling semver v1.0.25 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling futures-sink v0.3.31 [INFO] [stderr] Compiling futures-core v0.3.31 [INFO] [stderr] Compiling slab v0.4.9 [INFO] [stderr] Compiling pin-project-lite v0.2.16 [INFO] [stderr] Compiling futures-task v0.3.31 [INFO] [stderr] Compiling futures-io v0.3.31 [INFO] [stderr] Compiling pin-utils v0.1.0 [INFO] [stderr] Compiling futures-macro v0.3.31 [INFO] [stderr] Compiling cfg-if v1.0.0 [INFO] [stderr] Compiling futures-timer v3.0.3 [INFO] [stderr] Compiling futures-channel v0.3.31 [INFO] [stderr] Compiling aho-corasick v1.1.3 [INFO] [stderr] Compiling rustc_version v0.4.1 [INFO] [stderr] Compiling serde_json v1.0.139 [INFO] [stderr] Compiling rstest_macros v0.17.0 [INFO] [stderr] Compiling futures-util v0.3.31 [INFO] [stderr] Compiling regex-automata v0.4.9 [INFO] [stderr] Compiling schemars v0.8.21 [INFO] [stderr] Compiling ipnet v2.11.0 [INFO] [stderr] Compiling prefix-trie v0.2.5 [INFO] [stderr] Compiling regex v1.11.1 [INFO] [stderr] Compiling futures-executor v0.3.31 [INFO] [stderr] Compiling str_inflector v0.12.0 [INFO] [stderr] Compiling futures v0.3.31 [INFO] [stderr] Compiling buildstructor v0.5.4 [INFO] [stderr] Compiling strum_macros v0.24.3 [INFO] [stderr] Compiling icann-rdap-common v0.0.21 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:103:17 [INFO] [stdout] | [INFO] [stdout] 103 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [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 attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:219:17 [INFO] [stdout] | [INFO] [stdout] 219 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:239:17 [INFO] [stdout] | [INFO] [stdout] 239 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:258:17 [INFO] [stdout] | [INFO] [stdout] 258 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:302:17 [INFO] [stdout] | [INFO] [stdout] 302 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:333:17 [INFO] [stdout] | [INFO] [stdout] 333 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/httpdata.rs:7:48 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Serialize, Deserialize, Clone, Debug, Builder, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/httpdata.rs:24:1 [INFO] [stdout] | [INFO] [stdout] 24 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/autnum.rs:43:34 [INFO] [stdout] | [INFO] [stdout] 43 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/autnum.rs:70:1 [INFO] [stdout] | [INFO] [stdout] 70 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:12:34 [INFO] [stdout] | [INFO] [stdout] 12 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:24:34 [INFO] [stdout] | [INFO] [stdout] 24 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:37:34 [INFO] [stdout] | [INFO] [stdout] 37 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:60:34 [INFO] [stdout] | [INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:83:34 [INFO] [stdout] | [INFO] [stdout] 83 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:140:34 [INFO] [stdout] | [INFO] [stdout] 140 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:174:1 [INFO] [stdout] | [INFO] [stdout] 174 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/entity.rs:81:34 [INFO] [stdout] | [INFO] [stdout] 81 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/entity.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/error.rs:9:34 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/error.rs:24:1 [INFO] [stdout] | [INFO] [stdout] 24 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/help.rs:8:34 [INFO] [stdout] | [INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/help.rs:14:1 [INFO] [stdout] | [INFO] [stdout] 14 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:12:34 [INFO] [stdout] | [INFO] [stdout] 12 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:21:1 [INFO] [stdout] | [INFO] [stdout] 21 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:94:34 [INFO] [stdout] | [INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:115:1 [INFO] [stdout] | [INFO] [stdout] 115 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:149:34 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:187:1 [INFO] [stdout] | [INFO] [stdout] 187 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/redacted.rs:52:10 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Builder, Serialize, Deserialize, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:7:34 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:28:34 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:49:34 [INFO] [stdout] | [INFO] [stdout] 49 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:58:1 [INFO] [stdout] | [INFO] [stdout] 58 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:189:1 [INFO] [stdout] | [INFO] [stdout] 189 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:290:1 [INFO] [stdout] | [INFO] [stdout] 290 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:361:1 [INFO] [stdout] | [INFO] [stdout] 361 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:436:1 [INFO] [stdout] | [INFO] [stdout] 436 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:448:34 [INFO] [stdout] | [INFO] [stdout] 448 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:458:1 [INFO] [stdout] | [INFO] [stdout] 458 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:481:34 [INFO] [stdout] | [INFO] [stdout] 481 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:512:1 [INFO] [stdout] | [INFO] [stdout] 512 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling rstest v0.17.0 [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:103:17 [INFO] [stdout] | [INFO] [stdout] 103 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [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 attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:219:17 [INFO] [stdout] | [INFO] [stdout] 219 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:239:17 [INFO] [stdout] | [INFO] [stdout] 239 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:258:17 [INFO] [stdout] | [INFO] [stdout] 258 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:302:17 [INFO] [stdout] | [INFO] [stdout] 302 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:333:17 [INFO] [stdout] | [INFO] [stdout] 333 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/httpdata.rs:7:48 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Serialize, Deserialize, Clone, Debug, Builder, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/httpdata.rs:24:1 [INFO] [stdout] | [INFO] [stdout] 24 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/autnum.rs:43:34 [INFO] [stdout] | [INFO] [stdout] 43 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/autnum.rs:70:1 [INFO] [stdout] | [INFO] [stdout] 70 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:12:34 [INFO] [stdout] | [INFO] [stdout] 12 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:24:34 [INFO] [stdout] | [INFO] [stdout] 24 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:37:34 [INFO] [stdout] | [INFO] [stdout] 37 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:60:34 [INFO] [stdout] | [INFO] [stdout] 60 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:83:34 [INFO] [stdout] | [INFO] [stdout] 83 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:140:34 [INFO] [stdout] | [INFO] [stdout] 140 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:174:1 [INFO] [stdout] | [INFO] [stdout] 174 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/entity.rs:81:34 [INFO] [stdout] | [INFO] [stdout] 81 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/entity.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/error.rs:9:34 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/error.rs:24:1 [INFO] [stdout] | [INFO] [stdout] 24 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/help.rs:8:34 [INFO] [stdout] | [INFO] [stdout] 8 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/help.rs:14:1 [INFO] [stdout] | [INFO] [stdout] 14 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:12:34 [INFO] [stdout] | [INFO] [stdout] 12 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:21:1 [INFO] [stdout] | [INFO] [stdout] 21 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:94:34 [INFO] [stdout] | [INFO] [stdout] 94 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:115:1 [INFO] [stdout] | [INFO] [stdout] 115 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:149:34 [INFO] [stdout] | [INFO] [stdout] 149 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:187:1 [INFO] [stdout] | [INFO] [stdout] 187 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/redacted.rs:52:10 [INFO] [stdout] | [INFO] [stdout] 52 | #[derive(Builder, Serialize, Deserialize, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:7:34 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:28:34 [INFO] [stdout] | [INFO] [stdout] 28 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:49:34 [INFO] [stdout] | [INFO] [stdout] 49 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:58:1 [INFO] [stdout] | [INFO] [stdout] 58 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:189:1 [INFO] [stdout] | [INFO] [stdout] 189 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:290:1 [INFO] [stdout] | [INFO] [stdout] 290 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:361:1 [INFO] [stdout] | [INFO] [stdout] 361 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:436:1 [INFO] [stdout] | [INFO] [stdout] 436 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:448:34 [INFO] [stdout] | [INFO] [stdout] 448 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:458:1 [INFO] [stdout] | [INFO] [stdout] 458 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:481:34 [INFO] [stdout] | [INFO] [stdout] 481 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:512:1 [INFO] [stdout] | [INFO] [stdout] 512 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 25.16s [INFO] running `Command { std: "docker" "inspect" "d5463c11f2c1475ce58a73d283e8214512b91cc8e40ae76cd64e99512b920df8", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "d5463c11f2c1475ce58a73d283e8214512b91cc8e40ae76cd64e99512b920df8", kill_on_drop: false }` [INFO] [stdout] d5463c11f2c1475ce58a73d283e8214512b91cc8e40ae76cd64e99512b920df8 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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" "+beta-2025-02-18" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] a22e1284e55527436f0c9707b19406c11745be9fcf1cc2de1922a805620d1045 [INFO] running `Command { std: "docker" "start" "-a" "a22e1284e55527436f0c9707b19406c11745be9fcf1cc2de1922a805620d1045", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/contact/mod.rs:103:17 [INFO] [stderr] | [INFO] [stderr] 103 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/contact/mod.rs:219:17 [INFO] [stderr] | [INFO] [stderr] 219 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/contact/mod.rs:239:17 [INFO] [stderr] | [INFO] [stderr] 239 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/contact/mod.rs:258:17 [INFO] [stderr] | [INFO] [stderr] 258 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/contact/mod.rs:302:17 [INFO] [stderr] | [INFO] [stderr] 302 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/contact/mod.rs:333:17 [INFO] [stderr] | [INFO] [stderr] 333 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/httpdata.rs:7:48 [INFO] [stderr] | [INFO] [stderr] 7 | #[derive(Serialize, Deserialize, Clone, Debug, Builder, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/httpdata.rs:24:1 [INFO] [stderr] | [INFO] [stderr] 24 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/autnum.rs:43:34 [INFO] [stderr] | [INFO] [stderr] 43 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/autnum.rs:70:1 [INFO] [stderr] | [INFO] [stderr] 70 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/domain.rs:12:34 [INFO] [stderr] | [INFO] [stderr] 12 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/domain.rs:24:34 [INFO] [stderr] | [INFO] [stderr] 24 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/domain.rs:37:34 [INFO] [stderr] | [INFO] [stderr] 37 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/domain.rs:60:34 [INFO] [stderr] | [INFO] [stderr] 60 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/domain.rs:83:34 [INFO] [stderr] | [INFO] [stderr] 83 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/domain.rs:140:34 [INFO] [stderr] | [INFO] [stderr] 140 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/domain.rs:174:1 [INFO] [stderr] | [INFO] [stderr] 174 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/entity.rs:81:34 [INFO] [stderr] | [INFO] [stderr] 81 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/entity.rs:111:1 [INFO] [stderr] | [INFO] [stderr] 111 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/error.rs:9:34 [INFO] [stderr] | [INFO] [stderr] 9 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/error.rs:24:1 [INFO] [stderr] | [INFO] [stderr] 24 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/help.rs:8:34 [INFO] [stderr] | [INFO] [stderr] 8 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/help.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/nameserver.rs:12:34 [INFO] [stderr] | [INFO] [stderr] 12 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/nameserver.rs:21:1 [INFO] [stderr] | [INFO] [stderr] 21 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/nameserver.rs:94:34 [INFO] [stderr] | [INFO] [stderr] 94 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/nameserver.rs:115:1 [INFO] [stderr] | [INFO] [stderr] 115 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/network.rs:41:1 [INFO] [stderr] | [INFO] [stderr] 41 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/network.rs:81:1 [INFO] [stderr] | [INFO] [stderr] 81 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/network.rs:149:34 [INFO] [stderr] | [INFO] [stderr] 149 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/network.rs:187:1 [INFO] [stderr] | [INFO] [stderr] 187 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/redacted.rs:52:10 [INFO] [stderr] | [INFO] [stderr] 52 | #[derive(Builder, Serialize, Deserialize, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/search.rs:7:34 [INFO] [stderr] | [INFO] [stderr] 7 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/search.rs:16:1 [INFO] [stderr] | [INFO] [stderr] 16 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/search.rs:28:34 [INFO] [stderr] | [INFO] [stderr] 28 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/search.rs:37:1 [INFO] [stderr] | [INFO] [stderr] 37 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/search.rs:49:34 [INFO] [stderr] | [INFO] [stderr] 49 | #[derive(Serialize, Deserialize, Builder, Clone, PartialEq, Debug, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/search.rs:58:1 [INFO] [stderr] | [INFO] [stderr] 58 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/types.rs:189:1 [INFO] [stderr] | [INFO] [stderr] 189 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/types.rs:290:1 [INFO] [stderr] | [INFO] [stderr] 290 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/types.rs:361:1 [INFO] [stderr] | [INFO] [stderr] 361 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/types.rs:436:1 [INFO] [stderr] | [INFO] [stderr] 436 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/types.rs:448:34 [INFO] [stderr] | [INFO] [stderr] 448 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/types.rs:458:1 [INFO] [stderr] | [INFO] [stderr] 458 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/types.rs:481:34 [INFO] [stderr] | [INFO] [stderr] 481 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/response/types.rs:512:1 [INFO] [stderr] | [INFO] [stderr] 512 | #[buildstructor::buildstructor] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: no expected values for `feature` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `icann-rdap-common` (lib) generated 46 warnings [INFO] [stderr] warning: `icann-rdap-common` (lib test) generated 46 warnings (46 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.10s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/icann_rdap_common-80af1e125177bbff) [INFO] [stdout] [INFO] [stdout] running 230 tests [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_documentation_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_documentation_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_documentation_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_7 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_documentation_THEN_correct_result::case_5 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_documentation_THEN_correct_result::case_6 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_documentation_THEN_correct_result::case_7 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_documentation_THEN_correct_result::case_8 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_5 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_6 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_8 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_private_use_THEN_correct_result::case_9 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_02 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_03 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_documentation_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_04 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_01 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_07 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_08 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_09 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_05 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_06 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_with_empty_name_WHEN_checked_THEN_empty_name_check ... ok [INFO] [stdout] test check::domain::tests::GIVEN_domain_with_bad_ldh_WHEN_checked_THEN_invalid_ldh::case_2 ... ok [INFO] [stdout] test check::domain::tests::GIVEN_domain_with_bad_ldh_WHEN_checked_THEN_invalid_ldh::case_3 ... ok [INFO] [stdout] test check::domain::tests::GIVEN_domain_with_bad_unicode_WHEN_checked_THEN_invalid_ldh::case_1 ... ok [INFO] [stdout] test check::domain::tests::GIVEN_domain_with_bad_unicode_WHEN_checked_THEN_invalid_ldh::case_2 ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_with_empty_type_WHEN_checked_THEN_empty_type_check ... ok [INFO] [stdout] test check::httpdata::tests::check_rdap_media_with_charset_parameter ... ok [INFO] [stdout] test check::httpdata::tests::response_over_htttp_and_tig ... ok [INFO] [stdout] test check::httpdata::tests::check_cors_header_with_foo_and_tig ... ok [INFO] [stdout] test check::httpdata::tests::check_no_cors_header_and_tig ... ok [INFO] [stdout] test check::httpdata::tests::check_not_rdap_media ... ok [INFO] [stdout] test check::domain::tests::GIVEN_domain_with_mismatch_ldh_and_unicode_WHEN_checked_THEN_unicode_does_not_match ... ok [INFO] [stdout] test check::autnum::tests::GIVEN_autnum_WHEN_is_reserved_THEN_correct_result::case_10 ... ok [INFO] [stdout] test check::network::tests::GIVEN_cidr0_with_v6_length_WHEN_checked_THEN_no_length_check ... ok [INFO] [stdout] test check::httpdata::tests::check_cors_header_with_tig ... ok [INFO] [stdout] test check::nameserver::tests::GIVEN_nameserver_with_bad_v6s_WHEN_checked_THEN_ip_list_is_empty_check ... ok [INFO] [stdout] test check::httpdata::tests::check_exactly_rdap_media ... ok [INFO] [stdout] test check::network::tests::GIVEN_cidr0_with_v4_prefixex_WHEN_checked_THEN_no_prefix_check ... ok [INFO] [stdout] test check::httpdata::tests::given_response_is_over_https_and_tig ... ok [INFO] [stdout] test check::nameserver::tests::GIVEN_nameserver_with_bad_ldh_WHEN_checked_THEN_invalid_ldh::case_1 ... ok [INFO] [stdout] test check::nameserver::tests::GIVEN_nameserver_with_bad_ldh_WHEN_checked_THEN_invalid_ldh::case_2 ... ok [INFO] [stdout] test check::nameserver::tests::GIVEN_nameserver_with_empty_v4s_WHEN_checked_THEN_ip_list_is_empty_check ... ok [INFO] [stdout] test check::nameserver::tests::GIVEN_nameserver_with_empty_v6s_WHEN_checked_THEN_ip_list_is_empty_check ... ok [INFO] [stdout] test check::network::tests::GIVEN_cidr0_with_v4_length_WHEN_checked_THEN_no_length_check ... ok [INFO] [stdout] test check::domain::tests::GIVEN_domain_with_bad_ldh_WHEN_checked_THEN_invalid_ldh::case_1 ... ok [INFO] [stdout] test check::network::tests::GIVEN_cidr0_with_v6_prefixex_WHEN_checked_THEN_no_prefix_check ... ok [INFO] [stdout] test check::nameserver::tests::GIVEN_nameserver_with_bad_ldh_WHEN_checked_THEN_invalid_ldh::case_3 ... ok [INFO] [stdout] test check::nameserver::tests::GIVEN_nameserver_with_bad_v4s_WHEN_checked_THEN_ip_list_is_empty_check ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_bad_end_WHEN_checked_THEN_malformed_ip_check ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_bad_ip_version_WHEN_checked_THEN_version_match_check::case_1 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_bad_ip_version_WHEN_checked_THEN_version_match_check::case_3 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_bad_ip_version_WHEN_checked_THEN_version_match_check::case_2 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_bad_ip_version_WHEN_checked_THEN_version_match_check::case_4 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_end_before_start_WHEN_checked_THEN_end_before_start_check ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_empty_type_WHEN_checked_THEN_empty_type_check ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_ip_version_WHEN_checked_THEN_version_match_check::case_2 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_02 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_01 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_06 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_bad_start_WHEN_checked_THEN_malformed_ip_check ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_08 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_03 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_09 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_ip_version_WHEN_checked_THEN_version_match_check::case_1 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_04 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_no_end_WHEN_checked_THEN_missing_ip_check ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_07 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_12 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_05 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_10 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_no_start_WHEN_checked_THEN_missing_ip_check ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_domain_name_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::network::tests::GIVEN_network_with_empty_name_WHEN_checked_THEN_empty_name_check ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_domain_name_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_domain_name_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_domain_name_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::httpdata::tests::check_media_type_absent ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_domain_name_THEN_correct_result::case_5 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_11 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_string_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_string_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_string_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_string_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_tld_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_tld_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_tld_THEN_correct_result::case_5 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_unicode_domain_name_THEN_correct_result::case_5 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_tld_THEN_correct_result::case_6 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_whitespace_or_empty_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_tld_THEN_correct_result::case_7 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_unicode_domain_name_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_unicode_domain_name_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_unicode_domain_name_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_whitespace_or_empty_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_tld_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_unicode_domain_name_THEN_correct_result::case_6 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_unicode_domain_name_THEN_correct_result::case_7 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_tld_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_whitespace_or_empty_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_whitespace_or_empty_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_ldh_string_list_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_ldh_string_list_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_ldh_string_list_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_ldh_string_list_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_ldh_string_list_THEN_correct_result::case_5 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_unicode_domain_name_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_ldh_string_list_THEN_correct_result::case_6 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_4 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_5 ... ok [INFO] [stdout] test check::tests::GIVEN_info_subchecks_WHEN_traversed_for_info_THEN_found ... ok [INFO] [stdout] test check::tests::GIVEN_specwarn_checks_WHEN_traversed_for_info_THEN_not_found ... ok [INFO] [stdout] test check::types::tests::GIVEN_domain_with_self_link_WHEN_checked_THEN_no_check_found ... ok [INFO] [stdout] test check::tests::GIVEN_specwarn_subchecks_WHEN_traversed_for_info_THEN_not_found ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_ldh_string_list_THEN_correct_result::case_7 ... ok [INFO] [stdout] test check::types::tests::GIVEN_domain_with_no_links_WHEN_checked_THEN_object_classes_should_have_self_link ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_1 ... ok [INFO] [stdout] test check::types::tests::GIVEN_domain_with_no_self_link_WHEN_checked_THEN_object_classes_should_have_self_link ... ok [INFO] [stdout] test check::types::tests::GIVEN_event_with_bad_date_WHEN_checked_THEN_event_date_is_not_date ... ok [INFO] [stdout] test check::types::tests::GIVEN_event_with_no_date_WHEN_checked_THEN_event_date_absent ... ok [INFO] [stdout] test check::types::tests::GIVEN_event_with_no_action_WHEN_checked_THEN_event_action_absent ... ok [INFO] [stdout] test check::types::tests::GIVEN_link_with_no_href_property_WHEN_checked_THEN_link_missing_href_property ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_6 ... ok [INFO] [stdout] test check::types::tests::GIVEN_link_with_no_rel_property_WHEN_checked_THEN_link_missing_rel_property ... ok [INFO] [stdout] test check::tests::GIVEN_checks_and_subchecks_WHEN_traversed_THEN_tree_structure_shows_tree ... ok [INFO] [stdout] test check::tests::GIVEN_info_checks_WHEN_traversed_for_info_THEN_found ... ok [INFO] [stdout] test check::types::tests::GIVEN_link_with_no_val_property_WHEN_checked_THEN_link_missing_val_property ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_7 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_2 ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_empty_handle_WHEN_checked_THEN_handle_is_empty::case_1 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_3 ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_empty_status_WHEN_checked_THEN_status_is_empty::case_1 ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_empty_handle_WHEN_checked_THEN_handle_is_empty::case_2 ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_empty_status_WHEN_checked_THEN_status_is_empty::case_2 ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_empty_status_WHEN_checked_THEN_status_is_empty::case_4 ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_empty_status_WHEN_checked_THEN_status_is_empty::case_3 ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_no_links_WHEN_checked_THEN_no_object_classes_should_have_self_link ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_no_self_links_WHEN_checked_THEN_no_object_classes_should_have_self_link ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_self_link_WHEN_checked_THEN_no_check_found ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_self_link_and_notice_WHEN_checked_THEN_no_check_found ... ok [INFO] [stdout] test check::types::tests::GIVEN_notice_with_no_description_WHEN_checked_THEN_description_absent ... ok [INFO] [stdout] test check::types::tests::GIVEN_nameserver_with_self_link_and_remark_WHEN_checked_THEN_no_check_found ... ok [INFO] [stdout] test check::types::tests::GIVEN_object_related_link_with_non_rdap_type_WHEN_checked_THEN_related_link_not_rdap ... ok [INFO] [stdout] test check::types::tests::GIVEN_public_id_with_no_identifier_WHEN_checked_THEN_identifier_is_absent ... ok [INFO] [stdout] test check::types::tests::GIVEN_public_id_with_no_type_WHEN_checked_THEN_type_is_absent ... ok [INFO] [stdout] test check::types::tests::GIVEN_rdap_conformance_not_in_root_WHEN_checked_THEN_invalid_rdap_conformance_parent ... ok [INFO] [stdout] test check::types::tests::GIVEN_related_link_with_no_type_property_WHEN_checked_THEN_related_link_has_no_type ... ok [INFO] [stdout] test check::types::tests::GIVEN_self_link_with_no_type_property_WHEN_checked_THEN_self_link_has_no_type ... ok [INFO] [stdout] test check::types::tests::GIVEN_self_link_with_non_rdap_type_WHEN_checked_THEN_self_link_not_rdap ... ok [INFO] [stdout] test contact::to_vcard::tests::GIVEN_contact_WHEN_to_vcard_THEN_from_vcard_is_same ... ok [INFO] [stdout] test contact::from_vcard::tests::GIVEN_vcard_with_addr_street_array_WHEN_from_vcard_THEN_properties_are_correct ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_control_WHEN_should_cache_THEN_correc::case_1 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_control_WHEN_should_cache_THEN_correc::case_2 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_control_WHEN_should_cache_THEN_correc::case_3 ... ok [INFO] [stdout] test contact::from_vcard::tests::GIVEN_vcard_WHEN_from_vcard_THEN_properties_are_correct ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_01 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_02 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_03 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_04 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_08 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_09 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_data_and_data_cache_WHEN_to_lines_THEN_format_correct ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_10 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_lines_WHEN_from_lines_THEN_parse_correctly ... ok [INFO] [stdout] test iana::tests::GIVEN_autnum_bootstrap_with_match_WHEN_find_with_number_THEN_return_match::case_4 ... ok [INFO] [stdout] test iana::tests::GIVEN_domain_bootstrap_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test iana::tests::GIVEN_autnum_bootstrap_with_match_WHEN_find_with_number_THEN_return_match::case_5 ... ok [INFO] [stdout] test iana::tests::GIVEN_autnum_bootstrap_with_match_WHEN_find_with_string_THEN_return_match ... ok [INFO] [stdout] test iana::tests::GIVEN_domain_bootstrap_with_two_matching_WHEN_find_THEN_return_longest_match ... ok [INFO] [stdout] test iana::tests::GIVEN_domain_bootstrap_with_matching_WHEN_find_THEN_url_matches ... ok [INFO] [stdout] test iana::tests::GIVEN_ipv6_bootstrap_with_match_WHEN_find_with_ip_address_THEN_return_match ... ok [INFO] [stdout] test iana::tests::GIVEN_ipv4_bootstrap_with_match_WHEN_find_with_cidr_THEN_return_match ... ok [INFO] [stdout] test iana::tests::GIVEN_ipv6_bootstrap_with_match_WHEN_find_with_ip_cidr_THEN_return_match ... ok [INFO] [stdout] test iana::tests::GIVEN_registry_WHEN_get_file_name_THEN_correct_result::case_1 ... ok [INFO] [stdout] test iana::tests::GIVEN_ipv4_bootstrap_with_match_WHEN_find_with_ip_address_THEN_return_match ... ok [INFO] [stdout] test iana::tests::GIVEN_domain_bootstrap_with_root_WHEN_find_THEN_url_matches ... ok [INFO] [stdout] test iana::tests::GIVEN_registry_WHEN_get_file_name_THEN_correct_result::case_2 ... ok [INFO] [stdout] test iana::tests::GIVEN_registry_WHEN_get_file_name_THEN_correct_result::case_3 ... ok [INFO] [stdout] test iana::tests::GIVEN_registry_WHEN_get_file_name_THEN_correct_result::case_4 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_07 ... ok [INFO] [stdout] test iana::tests::GIVEN_tag_bootstrap_with_match_WHEN_find_with_tag_THEN_return_match ... ok [INFO] [stdout] test iana::tests::GIVEN_registry_WHEN_get_file_name_THEN_correct_result::case_5 ... ok [INFO] [stdout] test response::error::tests::GIVEN_error_code_301_WHEN_is_redirect_THEN_true ... ok [INFO] [stdout] test response::autnum::tests::GIVEN_autnum_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::nameserver::tests::GIVEN_nameserver_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::domain::tests::GIVEN_domain_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_05 ... ok [INFO] [stdout] test response::domain::tests::GIVEN_no_self_links_WHEN_set_self_link_THEN_link_is_only_one ... ok [INFO] [stdout] test iana::tests::GIVEN_autnum_bootstrap_with_match_WHEN_find_with_number_THEN_return_match::case_1 ... ok [INFO] [stdout] test response::entity::tests::GIVEN_entity_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::error::tests::GIVEN_error_code_404_WHEN_is_redirect_THEN_false ... ok [INFO] [stdout] test response::network::tests::GIVEN_network_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test iana::tests::GIVEN_one_http_and_https_url_WHEN_preferred_urls_THEN_return_https ... ok [INFO] [stdout] test iana::tests::GIVEN_one_url_WHEN_preferred_urls_THEN_that_is_the_one ... ok [INFO] [stdout] test response::redacted::tests::GIVEN_redaction_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test iana::tests::GIVEN_autnum_bootstrap_with_match_WHEN_find_with_number_THEN_return_match::case_2 ... ok [INFO] [stdout] test httpdata::tests::GIVEN_cache_data_and_max_age_WHEN_is_expired_THEN_correct::case_06 ... ok [INFO] [stdout] test iana::tests::GIVEN_autnum_bootstrap_with_match_WHEN_find_with_number_THEN_return_match::case_3 ... ok [INFO] [stdout] test iana::tests::GIVEN_autnum_bootstrap_with_match_WHEN_find_with_number_THEN_return_match::case_6 ... ok [INFO] [stdout] test response::types::tests::GIVEN_a_public_id_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::tests::GIVEN_autnum_response_WHEN_try_from_THEN_response_is_autnum ... ok [INFO] [stdout] test response::tests::GIVEN_domain_response_WHEN_try_from_THEN_response_is_domain ... ok [INFO] [stdout] test response::tests::GIVEN_error_response_WHEN_try_from_THEN_response_is_error ... ok [INFO] [stdout] test response::tests::GIVEN_entity_response_WHEN_try_from_THEN_response_is_entity ... ok [INFO] [stdout] test response::tests::GIVEN_nameserver_response_WHEN_try_from_THEN_response_is_nameserver ... ok [INFO] [stdout] test response::tests::GIVEN_help_response_WHEN_try_from_THEN_response_is_help ... ok [INFO] [stdout] test response::types::tests::GIVEN_a_notice_or_remark_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::tests::GIVEN_redaction_response_WHEN_has_extension_THEN_true ... ok [INFO] [stdout] test response::types::tests::GIVEN_an_array_of_links_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::tests::GIVEN_redaction_response_WHEN_try_from_THEN_response_is_lookup_with_redaction ... ok [INFO] [stdout] test response::tests::GIVEN_network_response_WHEN_try_from_THEN_response_is_network ... ok [INFO] [stdout] test response::redacted::tests::GIVEN_redaction_WHEN_set_THEN_success ... ok [INFO] [stdout] test response::types::tests::GIVEN_an_event_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::types::tests::GIVEN_no_links_WHEN_set_self_link_THEN_link_is_only_one ... ok [INFO] [stdout] test response::tests::GIVEN_redaction_response_WHEN_try_from_THEN_response_is_domain_search_results_with_redaction ... ok [INFO] [stdout] test response::types::tests::GIVEN_one_self_link_WHEN_set_self_link_THEN_link_is_only_one ... ok [INFO] [stdout] test response::types::tests::GIVEN_rdap_conformance_WHEN_serialize_THEN_array_of_strings ... ok [INFO] [stdout] test response::types::tests::GIVEN_remarks_WHEN_serialize_THEN_array_of_remark_structs ... ok [INFO] [stdout] test response::types::tests::GIVEN_no_self_links_WHEN_set_self_link_THEN_link_is_only_one ... ok [INFO] [stdout] test response::types::tests::GIVEN_notices_WHEN_serialize_THEN_array_of_notice_structs ... ok [INFO] [stdout] test response::types::tests::GIVEN_status_array_WHEN_serialize_THEN_array_of_strings ... ok [INFO] [stdout] test response::types::tests::GIVEN_an_array_of_links_with_one_lang_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::tests::GIVEN_entity_search_results_WHEN_try_from_THEN_response_is_entity_search_results ... ok [INFO] [stdout] test response::tests::GIVEN_domain_search_results_WHEN_try_from_THEN_response_is_domain_search_results ... ok [INFO] [stdout] test response::tests::GIVEN_entity_search_results_variant_WHEN_to_string_THEN_string_is_entity ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 230 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.19s [INFO] [stdout] [INFO] [stderr] Doc-tests icann_rdap_common [INFO] [stdout] [INFO] [stdout] running 36 tests [INFO] [stdout] test src/response/domain.rs - response::domain::Domain (line 112) ... FAILED [INFO] [stdout] test src/lib.rs - (line 25) ... FAILED [INFO] [stdout] test src/response/autnum.rs - response::autnum::Autnum::new_autnum (line 74) ... ok [INFO] [stdout] test src/response/autnum.rs - response::autnum::Autnum::basic (line 74) ... ok [INFO] [stdout] test src/contact/mod.rs - contact::Contact (line 93) ... ok [INFO] [stdout] test src/contact/mod.rs - contact (line 9) ... ok [INFO] [stdout] test src/lib.rs - (line 92) ... ok [INFO] [stdout] test src/contact/mod.rs - contact (line 37) ... ok [INFO] [stdout] test src/contact/to_vcard.rs - contact::to_vcard::Contact::to_vcard (line 11) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain::basic (line 178) ... ok [INFO] [stdout] test src/contact/mod.rs - contact (line 21) ... ok [INFO] [stdout] test src/lib.rs - (line 49) ... ok [INFO] [stdout] test src/lib.rs - (line 120) ... ok [INFO] [stdout] test src/lib.rs - (line 104) ... ok [INFO] [stdout] test src/contact/from_vcard.rs - contact::from_vcard::Contact::from_vcard (line 9) ... ok [INFO] [stdout] test src/response/autnum.rs - response::autnum::Autnum (line 15) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain::idn (line 233) ... ok [INFO] [stdout] test src/response/network.rs - response::network::Network (line 114) ... ok [INFO] [stdout] test src/response/network.rs - response::network::Network::basic (line 191) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain::new_idn (line 233) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain::new_ldh (line 178) ... ok [INFO] [stdout] test src/response/entity.rs - response::entity::Entity::new_handle (line 115) ... ok [INFO] [stdout] test src/response/nameserver.rs - response::nameserver::Nameserver::basic (line 119) ... ok [INFO] [stdout] test src/response/entity.rs - response::entity::Entity::basic (line 115) ... ok [INFO] [stdout] test src/response/network.rs - response::network::Network::new_network (line 191) ... ok [INFO] [stdout] test src/response/mod.rs - response::RdapResponse (line 58) ... ok [INFO] [stdout] test src/response/types.rs - response::types::Event (line 313) ... ok [INFO] [stdout] test src/response/nameserver.rs - response::nameserver::Nameserver::new_ldh (line 119) ... ok [INFO] [stdout] test src/response/types.rs - response::types::ExtensionId (line 38) ... ok [INFO] [stdout] test src/response/nameserver.rs - response::nameserver::Nameserver (line 47) ... ok [INFO] [stdout] test src/response/entity.rs - response::entity::Entity (line 20) ... ok [INFO] [stdout] test src/response/types.rs - response::types::ExtensionId (line 49) ... ok [INFO] [stdout] test src/response/types.rs - response::types::Link (line 136) ... ok [INFO] [stdout] test src/response/types.rs - response::types::ExtensionId (line 57) ... ok [INFO] [stdout] test src/response/types.rs - response::types::NoticeOrRemark (line 258) ... ok [INFO] [stdout] test src/response/types.rs - response::types::PublicId (line 416) ... ok [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] [INFO] [stdout] ---- src/response/domain.rs - response::domain::Domain (line 112) stdout ---- [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] ---- src/lib.rs - (line 25) stdout ---- [INFO] [stdout] Couldn't compile the test. [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] src/lib.rs - (line 25) [INFO] [stdout] src/response/domain.rs - response::domain::Domain (line 112) [INFO] [stdout] [INFO] [stdout] test result: FAILED. 34 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 16.68s [INFO] [stdout] [INFO] [stderr] error: doctest failed, to rerun pass `--doc` [INFO] running `Command { std: "docker" "inspect" "a22e1284e55527436f0c9707b19406c11745be9fcf1cc2de1922a805620d1045", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a22e1284e55527436f0c9707b19406c11745be9fcf1cc2de1922a805620d1045", kill_on_drop: false }` [INFO] [stdout] a22e1284e55527436f0c9707b19406c11745be9fcf1cc2de1922a805620d1045