[INFO] fetching crate icann-rdap-common 0.0.22... [INFO] testing icann-rdap-common-0.0.22 against master#cdb45c87e2cd43495379f7e867e3cc15dcee9f93 for pr-145838-1 [INFO] extracting crate icann-rdap-common 0.0.22 into /workspace/builds/worker-6-tc1/source [INFO] started tweaking crates.io crate icann-rdap-common 0.0.22 [INFO] finished tweaking crates.io crate icann-rdap-common 0.0.22 [INFO] tweaked toml for crates.io crate icann-rdap-common 0.0.22 written to /workspace/builds/worker-6-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate icann-rdap-common 0.0.22 on toolchain cdb45c87e2cd43495379f7e867e3cc15dcee9f93 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 105 packages to latest compatible versions [INFO] [stderr] Adding buildstructor v0.5.4 (available: v0.6.0) [INFO] [stderr] Adding prefix-trie v0.2.5 (available: v0.8.1) [INFO] [stderr] Adding rstest v0.17.0 (available: v0.26.1) [INFO] [stderr] Adding strum v0.24.1 (available: v0.27.2) [INFO] [stderr] Adding strum_macros v0.24.3 (available: v0.27.2) [INFO] [stderr] Adding thiserror v1.0.69 (available: v2.0.16) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded buildstructor v0.5.4 [INFO] [stderr] Downloaded prefix-trie v0.2.5 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 1d986668f666d4cb2324caa7b6c6dda648c089726883777799fa39063132f814 [INFO] running `Command { std: "docker" "start" "-a" "1d986668f666d4cb2324caa7b6c6dda648c089726883777799fa39063132f814", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "1d986668f666d4cb2324caa7b6c6dda648c089726883777799fa39063132f814", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "1d986668f666d4cb2324caa7b6c6dda648c089726883777799fa39063132f814", kill_on_drop: false }` [INFO] [stdout] 1d986668f666d4cb2324caa7b6c6dda648c089726883777799fa39063132f814 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 6db67a74ba6f65f4c328f88516a18980d20a38cc99a5b682b9c0f10a30fc70f4 [INFO] running `Command { std: "docker" "start" "-a" "6db67a74ba6f65f4c328f88516a18980d20a38cc99a5b682b9c0f10a30fc70f4", kill_on_drop: false }` [INFO] [stderr] Compiling schemars v0.8.22 [INFO] [stderr] Compiling regex-automata v0.4.10 [INFO] [stderr] Compiling serde_derive_internals v0.29.1 [INFO] [stderr] Compiling serde_json v1.0.143 [INFO] [stderr] Compiling try_match_inner v0.5.2 [INFO] [stderr] Compiling const_format_proc_macros v0.2.34 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling icu_normalizer v2.0.0 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling chrono v0.4.41 [INFO] [stderr] Compiling try_match v0.4.2 [INFO] [stderr] Compiling const_format v0.2.34 [INFO] [stderr] Compiling cidr v0.3.1 [INFO] [stderr] Compiling idna_adapter v1.2.1 [INFO] [stderr] Compiling idna v1.1.0 [INFO] [stderr] Compiling schemars_derive v0.8.22 [INFO] [stderr] Compiling strum v0.24.1 [INFO] [stderr] Compiling strum_macros v0.24.3 [INFO] [stderr] Compiling regex v1.11.2 [INFO] [stderr] Compiling ipnet v2.11.0 [INFO] [stderr] Compiling str_inflector v0.12.0 [INFO] [stderr] Compiling buildstructor v0.5.4 [INFO] [stderr] Compiling prefix-trie v0.2.5 [INFO] [stderr] Compiling icann-rdap-common v0.0.22 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:147:1 [INFO] [stdout] | [INFO] [stdout] 147 | #[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: `#[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:256:17 [INFO] [stdout] | [INFO] [stdout] 256 | #[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:294:1 [INFO] [stdout] | [INFO] [stdout] 294 | #[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/contact/mod.rs:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[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/contact/mod.rs:403:1 [INFO] [stdout] | [INFO] [stdout] 403 | #[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/contact/mod.rs:449:1 [INFO] [stdout] | [INFO] [stdout] 449 | #[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/httpdata.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | #[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:72:1 [INFO] [stdout] | [INFO] [stdout] 72 | #[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/common.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/domain.rs:19:34 [INFO] [stdout] | [INFO] [stdout] 19 | #[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:1 [INFO] [stdout] | [INFO] [stdout] 60 | #[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:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[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:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[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:312:1 [INFO] [stdout] | [INFO] [stdout] 312 | #[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:471:1 [INFO] [stdout] | [INFO] [stdout] 471 | #[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:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[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:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | #[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: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/nameserver.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | #[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:143:1 [INFO] [stdout] | [INFO] [stdout] 143 | #[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:51:1 [INFO] [stdout] | [INFO] [stdout] 51 | #[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:94:1 [INFO] [stdout] | [INFO] [stdout] 94 | #[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:202:1 [INFO] [stdout] | [INFO] [stdout] 202 | #[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/obj_common.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | #[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:59:10 [INFO] [stdout] | [INFO] [stdout] 59 | #[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:19:1 [INFO] [stdout] | [INFO] [stdout] 19 | #[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:53:1 [INFO] [stdout] | [INFO] [stdout] 53 | #[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:87:1 [INFO] [stdout] | [INFO] [stdout] 87 | #[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:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[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:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[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:548:1 [INFO] [stdout] | [INFO] [stdout] 548 | #[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:637:1 [INFO] [stdout] | [INFO] [stdout] 637 | #[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 27.56s [INFO] running `Command { std: "docker" "inspect" "6db67a74ba6f65f4c328f88516a18980d20a38cc99a5b682b9c0f10a30fc70f4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6db67a74ba6f65f4c328f88516a18980d20a38cc99a5b682b9c0f10a30fc70f4", kill_on_drop: false }` [INFO] [stdout] 6db67a74ba6f65f4c328f88516a18980d20a38cc99a5b682b9c0f10a30fc70f4 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 22040f884abddea4f0c83a4267f73c160424d92e9f8c761c34575ceb313b4211 [INFO] running `Command { std: "docker" "start" "-a" "22040f884abddea4f0c83a4267f73c160424d92e9f8c761c34575ceb313b4211", kill_on_drop: false }` [INFO] [stderr] Compiling futures-macro v0.3.31 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling serde_json v1.0.143 [INFO] [stderr] Compiling rstest_macros v0.17.0 [INFO] [stderr] Compiling str_inflector v0.12.0 [INFO] [stderr] Compiling buildstructor v0.5.4 [INFO] [stderr] Compiling futures-util v0.3.31 [INFO] [stderr] Compiling schemars v0.8.22 [INFO] [stderr] Compiling ipnet v2.11.0 [INFO] [stderr] Compiling prefix-trie v0.2.5 [INFO] [stderr] Compiling futures-executor v0.3.31 [INFO] [stderr] Compiling futures v0.3.31 [INFO] [stderr] Compiling strum_macros v0.24.3 [INFO] [stderr] Compiling icann-rdap-common v0.0.22 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:147:1 [INFO] [stdout] | [INFO] [stdout] 147 | #[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: `#[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:256:17 [INFO] [stdout] | [INFO] [stdout] 256 | #[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:294:1 [INFO] [stdout] | [INFO] [stdout] 294 | #[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/contact/mod.rs:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[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/contact/mod.rs:403:1 [INFO] [stdout] | [INFO] [stdout] 403 | #[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/contact/mod.rs:449:1 [INFO] [stdout] | [INFO] [stdout] 449 | #[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/httpdata.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | #[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:72:1 [INFO] [stdout] | [INFO] [stdout] 72 | #[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/common.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/domain.rs:19:34 [INFO] [stdout] | [INFO] [stdout] 19 | #[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:1 [INFO] [stdout] | [INFO] [stdout] 60 | #[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:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[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:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[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:312:1 [INFO] [stdout] | [INFO] [stdout] 312 | #[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:471:1 [INFO] [stdout] | [INFO] [stdout] 471 | #[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:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[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:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | #[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: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/nameserver.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | #[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:143:1 [INFO] [stdout] | [INFO] [stdout] 143 | #[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:51:1 [INFO] [stdout] | [INFO] [stdout] 51 | #[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:94:1 [INFO] [stdout] | [INFO] [stdout] 94 | #[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:202:1 [INFO] [stdout] | [INFO] [stdout] 202 | #[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/obj_common.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | #[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:59:10 [INFO] [stdout] | [INFO] [stdout] 59 | #[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:19:1 [INFO] [stdout] | [INFO] [stdout] 19 | #[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:53:1 [INFO] [stdout] | [INFO] [stdout] 53 | #[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:87:1 [INFO] [stdout] | [INFO] [stdout] 87 | #[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:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[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:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[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:548:1 [INFO] [stdout] | [INFO] [stdout] 548 | #[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:637:1 [INFO] [stdout] | [INFO] [stdout] 637 | #[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:147:1 [INFO] [stdout] | [INFO] [stdout] 147 | #[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: `#[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:256:17 [INFO] [stdout] | [INFO] [stdout] 256 | #[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:294:1 [INFO] [stdout] | [INFO] [stdout] 294 | #[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/contact/mod.rs:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[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/contact/mod.rs:403:1 [INFO] [stdout] | [INFO] [stdout] 403 | #[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/contact/mod.rs:449:1 [INFO] [stdout] | [INFO] [stdout] 449 | #[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/httpdata.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | #[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:72:1 [INFO] [stdout] | [INFO] [stdout] 72 | #[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/common.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/domain.rs:19:34 [INFO] [stdout] | [INFO] [stdout] 19 | #[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:1 [INFO] [stdout] | [INFO] [stdout] 60 | #[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:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[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:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[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:312:1 [INFO] [stdout] | [INFO] [stdout] 312 | #[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:471:1 [INFO] [stdout] | [INFO] [stdout] 471 | #[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:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[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:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | #[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: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/nameserver.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | #[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:143:1 [INFO] [stdout] | [INFO] [stdout] 143 | #[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:51:1 [INFO] [stdout] | [INFO] [stdout] 51 | #[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:94:1 [INFO] [stdout] | [INFO] [stdout] 94 | #[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:202:1 [INFO] [stdout] | [INFO] [stdout] 202 | #[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/obj_common.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | #[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:59:10 [INFO] [stdout] | [INFO] [stdout] 59 | #[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:19:1 [INFO] [stdout] | [INFO] [stdout] 19 | #[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:53:1 [INFO] [stdout] | [INFO] [stdout] 53 | #[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:87:1 [INFO] [stdout] | [INFO] [stdout] 87 | #[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:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[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:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[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:548:1 [INFO] [stdout] | [INFO] [stdout] 548 | #[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:637:1 [INFO] [stdout] | [INFO] [stdout] 637 | #[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 34.68s [INFO] running `Command { std: "docker" "inspect" "22040f884abddea4f0c83a4267f73c160424d92e9f8c761c34575ceb313b4211", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "22040f884abddea4f0c83a4267f73c160424d92e9f8c761c34575ceb313b4211", kill_on_drop: false }` [INFO] [stdout] 22040f884abddea4f0c83a4267f73c160424d92e9f8c761c34575ceb313b4211 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] 35fbbae191f389ba153a8be2a67568b8305fa01b375e9164aed796168f019dad [INFO] running `Command { std: "docker" "start" "-a" "35fbbae191f389ba153a8be2a67568b8305fa01b375e9164aed796168f019dad", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stderr] --> src/contact/mod.rs:147:1 [INFO] [stderr] | [INFO] [stderr] 147 | #[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: `#[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:256:17 [INFO] [stderr] | [INFO] [stderr] 256 | #[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:294:1 [INFO] [stderr] | [INFO] [stderr] 294 | #[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/contact/mod.rs:359:1 [INFO] [stderr] | [INFO] [stderr] 359 | #[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/contact/mod.rs:403:1 [INFO] [stderr] | [INFO] [stderr] 403 | #[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/contact/mod.rs:449:1 [INFO] [stderr] | [INFO] [stderr] 449 | #[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/httpdata.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | #[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:72:1 [INFO] [stderr] | [INFO] [stderr] 72 | #[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/common.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/domain.rs:19:34 [INFO] [stderr] | [INFO] [stderr] 19 | #[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:1 [INFO] [stderr] | [INFO] [stderr] 60 | #[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:121:1 [INFO] [stderr] | [INFO] [stderr] 121 | #[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:192:1 [INFO] [stderr] | [INFO] [stderr] 192 | #[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:312:1 [INFO] [stderr] | [INFO] [stderr] 312 | #[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:471:1 [INFO] [stderr] | [INFO] [stderr] 471 | #[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:121:1 [INFO] [stderr] | [INFO] [stderr] 121 | #[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:36:1 [INFO] [stderr] | [INFO] [stderr] 36 | #[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: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/nameserver.rs:25:1 [INFO] [stderr] | [INFO] [stderr] 25 | #[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:143:1 [INFO] [stderr] | [INFO] [stderr] 143 | #[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:51:1 [INFO] [stderr] | [INFO] [stderr] 51 | #[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:94:1 [INFO] [stderr] | [INFO] [stderr] 94 | #[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:202:1 [INFO] [stderr] | [INFO] [stderr] 202 | #[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/obj_common.rs:40:1 [INFO] [stderr] | [INFO] [stderr] 40 | #[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:59:10 [INFO] [stderr] | [INFO] [stderr] 59 | #[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:19:1 [INFO] [stderr] | [INFO] [stderr] 19 | #[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:53:1 [INFO] [stderr] | [INFO] [stderr] 53 | #[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:87:1 [INFO] [stderr] | [INFO] [stderr] 87 | #[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:192:1 [INFO] [stderr] | [INFO] [stderr] 192 | #[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:359:1 [INFO] [stderr] | [INFO] [stderr] 359 | #[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:548:1 [INFO] [stderr] | [INFO] [stderr] 548 | #[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:637:1 [INFO] [stderr] | [INFO] [stderr] 637 | #[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 32 warnings [INFO] [stderr] warning: `icann-rdap-common` (lib test) generated 32 warnings (32 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.16s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/icann_rdap_common-7846d031c3b2bb5c) [INFO] [stdout] [INFO] [stdout] running 266 tests [INFO] [stdout] test check::autnum::tests::check_autnum_is_documentation::case_2 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_documentation::case_4 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_documentation::case_7 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_documentation::case_8 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_1 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_3 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_4 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_5 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_6 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_7 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_9 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_01 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_documentation::case_3 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_02 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_03 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_05 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_04 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_07 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_06 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_09 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_08 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_reserved::case_10 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_with_empty_name ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_with_empty_type ... ok [INFO] [stdout] test check::domain::tests::test_check_for_bad_ldh::case_1 ... ok [INFO] [stdout] test check::domain::tests::test_check_for_bad_ldh::case_3 ... ok [INFO] [stdout] test check::domain::tests::test_check_for_bad_ldh::case_2 ... ok [INFO] [stdout] test check::domain::tests::test_check_for_ldh_unicode_mismatch ... ok [INFO] [stdout] test check::domain::tests::test_check_for_bad_unicode::case_2 ... ok [INFO] [stdout] test check::domain::tests::test_delegation_signed_as_string ... ok [INFO] [stdout] test check::domain::tests::test_ds_data_attributes_as_number ... ok [INFO] [stdout] test check::domain::tests::test_ds_data_attributes_as_string ... ok [INFO] [stdout] test check::domain::tests::test_check_for_bad_unicode::case_1 ... ok [INFO] [stdout] test check::domain::tests::test_ds_data_attributes_out_of_range ... ok [INFO] [stdout] test check::domain::tests::test_delegation_signed_as_bool ... ok [INFO] [stdout] test check::domain::tests::test_key_data_attributes_as_string ... ok [INFO] [stdout] test check::domain::tests::test_key_data_attributes_out_of_range ... ok [INFO] [stdout] test check::domain::tests::test_max_sig_life_as_number ... ok [INFO] [stdout] test check::domain::tests::test_max_sig_life_as_string ... ok [INFO] [stdout] test check::domain::tests::test_zone_signed_as_string ... ok [INFO] [stdout] test check::httpdata::tests::check_cors_header_with_foo_and_tig ... ok [INFO] [stdout] test check::domain::tests::test_zone_signed_as_bool ... ok [INFO] [stdout] test check::httpdata::tests::check_cors_header_with_tig ... ok [INFO] [stdout] test check::domain::tests::test_key_data_attributes_as_number ... ok [INFO] [stdout] test check::httpdata::tests::check_media_type_absent ... ok [INFO] [stdout] test check::httpdata::tests::check_exactly_rdap_media ... 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::httpdata::tests::check_rdap_media_with_charset_parameter ... ok [INFO] [stdout] test check::httpdata::tests::given_response_is_over_https_and_tig ... ok [INFO] [stdout] test check::httpdata::tests::response_over_htttp_and_tig ... ok [INFO] [stdout] test check::nameserver::tests::check_nameserver_with_bad_ldh::case_1 ... ok [INFO] [stdout] test check::nameserver::tests::check_nameserver_with_bad_ldh::case_2 ... ok [INFO] [stdout] test check::nameserver::tests::check_nameserver_with_bad_ldh::case_3 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_2 ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_private_use::case_8 ... ok [INFO] [stdout] test check::nameserver::tests::check_nameserver_with_bad_v4s ... ok [INFO] [stdout] test check::nameserver::tests::check_nameserver_with_bad_v6s ... ok [INFO] [stdout] test check::nameserver::tests::check_nameserver_with_empty_v4s ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_documentation::case_1 ... ok [INFO] [stdout] test check::nameserver::tests::check_nameserver_with_empty_v6s ... ok [INFO] [stdout] test check::network::tests::check_cidr0_with_v4_length ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_documentation::case_5 ... ok [INFO] [stdout] test check::network::tests::check_cidr0_with_v4_prefixex ... ok [INFO] [stdout] test check::network::tests::check_network_with_bad_end ... ok [INFO] [stdout] test check::network::tests::check_cidr0_with_v6_length ... ok [INFO] [stdout] test check::network::tests::check_cidr0_with_v6_prefixex ... ok [INFO] [stdout] test check::autnum::tests::check_autnum_is_documentation::case_6 ... ok [INFO] [stdout] test check::network::tests::check_network_with_bad_ip_version::case_2 ... ok [INFO] [stdout] test check::network::tests::check_network_with_bad_ip_version::case_1 ... ok [INFO] [stdout] test check::network::tests::check_network_with_ip_version::case_2 ... ok [INFO] [stdout] test check::network::tests::check_network_with_bad_ip_version::case_3 ... ok [INFO] [stdout] test check::network::tests::check_network_with_bad_ip_version::case_4 ... ok [INFO] [stdout] test check::network::tests::check_network_with_bad_start ... ok [INFO] [stdout] test check::network::tests::check_network_with_empty_name ... ok [INFO] [stdout] test check::network::tests::check_network_with_empty_type ... ok [INFO] [stdout] test check::network::tests::check_network_with_end_before_start ... ok [INFO] [stdout] test check::network::tests::check_network_with_ip_version::case_1 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_04 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_06 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_07 ... ok [INFO] [stdout] test check::network::tests::check_network_with_no_end ... ok [INFO] [stdout] test check::network::tests::check_network_with_no_start ... 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_02 ... 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_05 ... 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_char_WHEN_is_ldh_THEN_correct_result::case_09 ... ok [INFO] [stdout] test check::string::tests::GIVEN_char_WHEN_is_ldh_THEN_correct_result::case_10 ... 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_char_WHEN_is_ldh_THEN_correct_result::case_12 ... ok [INFO] [stdout] test check::string::tests::GIVEN_string_WHEN_is_ldh_domain_name_THEN_correct_result::case_1 ... 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_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::string::tests::GIVEN_string_WHEN_is_ldh_domain_name_THEN_correct_result::case_5 ... 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_3 ... 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_tld_THEN_correct_result::case_1 ... 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_tld_THEN_correct_result::case_3 ... 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_tld_THEN_correct_result::case_6 ... 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_unicode_domain_name_THEN_correct_result::case_4 ... 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_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_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_2 ... 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_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_list_WHEN_is_ldh_string_list_THEN_correct_result::case_6 ... 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::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_1 ... 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::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_3 ... 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::string::tests::GIVEN_string_list_WHEN_is_whitespace_or_empty_THEN_correct_result::case_6 ... 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::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::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::tests::GIVEN_specwarn_subchecks_WHEN_traversed_for_info_THEN_not_found ... ok [INFO] [stdout] test check::types::tests::check_link_with_no_href_property ... ok [INFO] [stdout] test check::types::tests::check_link_with_no_rel_property ... ok [INFO] [stdout] test check::types::tests::check_link_with_no_val_property ... ok [INFO] [stdout] test check::types::tests::test_domain_with_no_links ... ok [INFO] [stdout] test check::types::tests::test_domain_with_no_self_link ... ok [INFO] [stdout] test check::types::tests::test_domain_with_self_link ... ok [INFO] [stdout] test check::types::tests::test_event_with_bad_date ... ok [INFO] [stdout] test check::types::tests::test_event_with_no_action ... ok [INFO] [stdout] test check::types::tests::test_event_with_no_date ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_empty_handle::case_1 ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_empty_handle::case_2 ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_empty_status::case_1 ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_empty_status::case_2 ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_empty_status::case_3 ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_empty_status::case_4 ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_no_links ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_no_self_links ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_self_link ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_self_link_and_notice ... ok [INFO] [stdout] test check::types::tests::test_nameserver_with_self_link_and_remark ... ok [INFO] [stdout] test check::types::tests::test_notice_with_no_description ... ok [INFO] [stdout] test check::types::tests::test_object_related_link_with_non_rdap_type ... ok [INFO] [stdout] test check::types::tests::test_public_id_with_no_identifier ... ok [INFO] [stdout] test check::types::tests::test_public_id_with_no_type ... ok [INFO] [stdout] test check::types::tests::test_rdap_conformance_not_in_root ... ok [INFO] [stdout] test check::types::tests::test_related_link_with_no_type_property ... ok [INFO] [stdout] test check::types::tests::test_self_link_with_no_type_property ... ok [INFO] [stdout] test check::types::tests::test_self_link_with_non_rdap_type ... ok [INFO] [stdout] test contact::from_vcard::tests::GIVEN_vcard_WHEN_from_vcard_THEN_properties_are_correct ... 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 contact::to_vcard::tests::GIVEN_contact_WHEN_to_vcard_THEN_from_vcard_is_same ... ok [INFO] [stdout] test httpdata::tests::test_cache_control::case_1 ... ok [INFO] [stdout] test httpdata::tests::test_cache_control::case_2 ... ok [INFO] [stdout] test httpdata::tests::test_cache_control::case_3 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_01 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_02 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_03 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_04 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_05 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_06 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_07 ... ok [INFO] [stdout] test iana::tests::GIVEN_autnum_bootstrap_with_match_WHEN_find_with_number_THEN_return_match::case_1 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_08 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_09 ... ok [INFO] [stdout] test httpdata::tests::test_cache_data_and_max_age_is_expired::case_10 ... ok [INFO] [stdout] test httpdata::tests::test_data_and_data_cache_to_lines ... ok [INFO] [stdout] test httpdata::tests::test_from_lines ... 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_4 ... 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_number_THEN_return_match::case_6 ... ok [INFO] [stdout] test iana::tests::GIVEN_domain_bootstrap_with_matching_WHEN_find_THEN_url_matches ... 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_root_WHEN_find_THEN_url_matches ... ok [INFO] [stdout] test iana::tests::GIVEN_domain_bootstrap_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_domain_bootstrap_with_two_matching_WHEN_find_THEN_return_longest_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_ipv4_bootstrap_with_match_WHEN_find_with_ip_address_THEN_return_match ... 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_autnum_bootstrap_with_match_WHEN_find_with_number_THEN_return_match::case_2 ... 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_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 iana::tests::GIVEN_tag_bootstrap_with_match_WHEN_find_with_tag_THEN_return_match ... ok [INFO] [stdout] test iana::tests::GIVEN_one_url_WHEN_preferred_urls_THEN_that_is_the_one ... ok [INFO] [stdout] test iana::tests::GIVEN_registry_WHEN_get_file_name_THEN_correct_result::case_5 ... ok [INFO] [stdout] test iana::tests::GIVEN_registry_WHEN_get_file_name_THEN_correct_result::case_1 ... ok [INFO] [stdout] test response::autnum::tests::GIVEN_autnum_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::lenient::tests::test_boolish_deserialize_bool_false ... ok [INFO] [stdout] test response::lenient::tests::test_boolish_deserialize_bool_true ... ok [INFO] [stdout] test response::lenient::tests::test_boolish_deserialize_string_false ... ok [INFO] [stdout] test response::lenient::tests::test_boolish_deserialize_string_true ... ok [INFO] [stdout] test response::lenient::tests::test_boolish_is_false ... ok [INFO] [stdout] test response::lenient::tests::test_boolish_is_true ... ok [INFO] [stdout] test response::lenient::tests::test_boolish_serialize_bool ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_as_smaller_types ... ok [INFO] [stdout] test response::domain::tests::GIVEN_domain_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_as_u64_number ... ok [INFO] [stdout] test response::lenient::tests::test_boolish_from_bool ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_as_u64_string_invalid ... ok [INFO] [stdout] test response::error::tests::GIVEN_error_code_301_WHEN_is_redirect_THEN_true ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_display_number ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_display_string_invalid ... 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::domain::tests::GIVEN_no_self_links_WHEN_set_self_link_THEN_link_is_only_one ... ok [INFO] [stdout] test response::lenient::tests::test_vectorstringish_deserialize_many ... ok [INFO] [stdout] test response::lenient::tests::test_vectorstringish_deserialize_one ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_display_string_valid ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_serialize_number ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_deserialize_number ... ok [INFO] [stdout] test response::lenient::tests::test_numberish_deserialize_string ... ok [INFO] [stdout] test response::redacted::tests::GIVEN_redaction_WHEN_set_THEN_success ... ok [INFO] [stdout] test response::lenient::tests::test_vectorstringish_serialize_one ... ok [INFO] [stdout] test response::nameserver::tests::GIVEN_nameserver_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::network::tests::GIVEN_network_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::tests::test_get_related_for_non_rel_link ... ok [INFO] [stdout] test response::tests::test_get_related_for_rel_link_that_look_like_rdap ... ok [INFO] [stdout] test response::tests::test_get_related_for_rel_with_rdap_type_link ... ok [INFO] [stdout] test response::lenient::tests::test_vectorstringish_serialize_many ... ok [INFO] [stdout] test response::tests::test_redaction_response_domain_search ... ok [INFO] [stdout] test response::redacted::tests::GIVEN_redaction_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::tests::test_response_is_autnum ... ok [INFO] [stdout] test response::tests::test_resopnse_is_domain ... ok [INFO] [stdout] test response::tests::test_get_related_for_rel_link ... ok [INFO] [stdout] test response::tests::test_redaction_response_gets_object ... ok [INFO] [stdout] test response::tests::test_redaction_response_has_extension ... ok [INFO] [stdout] test response::tests::test_response_is_help ... ok [INFO] [stdout] test response::tests::test_response_is_nameserver ... ok [INFO] [stdout] test response::tests::test_response_is_network ... ok [INFO] [stdout] test response::types::tests::GIVEN_an_array_of_links_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::tests::test_response_is_error ... ok [INFO] [stdout] test response::tests::test_response_is_entity ... ok [INFO] [stdout] test response::types::tests::GIVEN_a_public_id_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::types::tests::GIVEN_a_notice_or_remark_WHEN_deserialize_THEN_success ... ok [INFO] [stdout] test response::types::tests::GIVEN_an_array_of_links_with_one_lang_WHEN_deserialize_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::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_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::tests::test_string_is_entity_search_results ... ok [INFO] [stdout] test response::tests::test_response_is_entity_search_results ... ok [INFO] [stdout] test response::tests::test_response_is_domain_search_results ... ok [INFO] [stderr] Doc-tests icann_rdap_common [INFO] [stdout] [INFO] [stdout] test result: ok. 266 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.19s [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 44 tests [INFO] [stdout] test src/contact/mod.rs - contact (line 9) ... ok [INFO] [stdout] test src/check/string.rs - check::string::StringCheck (line 4) ... ok [INFO] [stdout] test src/check/string.rs - check::string::StringListCheck (line 69) ... ok [INFO] [stdout] test src/contact/mod.rs - contact::Contact (line 95) ... ok [INFO] [stdout] test src/contact/from_vcard.rs - contact::from_vcard::Contact::from_vcard (line 9) ... ok [INFO] [stdout] test src/check/string.rs - check::string::CharCheck (line 107) ... ok [INFO] [stdout] test src/contact/mod.rs - contact (line 37) ... ok [INFO] [stdout] test src/contact/mod.rs - contact (line 21) ... ok [INFO] [stdout] test src/lib.rs - (line 104) ... ok [INFO] [stdout] test src/lib.rs - (line 49) ... ok [INFO] [stdout] test src/lib.rs - (line 120) ... ok [INFO] [stdout] test src/contact/to_vcard.rs - contact::to_vcard::Contact::to_vcard (line 11) ... ok [INFO] [stdout] test src/lib.rs - (line 92) ... ok [INFO] [stdout] test src/response/autnum.rs - response::autnum::Autnum (line 18) ... ok [INFO] [stdout] test src/response/autnum.rs - response::autnum::Autnum::new (line 76) ... ok [INFO] [stdout] test src/response/autnum.rs - response::autnum::Autnum::builder (line 76) ... ok [INFO] [stdout] test src/lib.rs - (line 25) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain::builder (line 475) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain (line 401) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain::idn (line 532) ... ok [INFO] [stdout] test src/response/entity.rs - response::entity::Entity (line 27) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain::new_idn (line 532) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::SecureDns (line 253) ... ok [INFO] [stdout] test src/response/lenient.rs - response::lenient::Boolish (line 177) ... ok [INFO] [stdout] test src/response/entity.rs - response::entity::Entity::builder (line 125) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain::new (line 475) ... ok [INFO] [stdout] test src/response/entity.rs - response::entity::Entity::new (line 125) ... ok [INFO] [stdout] test src/response/lenient.rs - response::lenient::VectorStringish (line 21) ... ok [INFO] [stdout] test src/response/domain.rs - response::domain::Domain (line 369) ... ok [INFO] [stdout] test src/response/lenient.rs - response::lenient::Numberish (line 247) ... ok [INFO] [stdout] test src/response/network.rs - response::network::Network (line 128) ... ok [INFO] [stdout] test src/response/mod.rs - response::RdapResponse (line 86) ... ok [INFO] [stdout] test src/response/nameserver.rs - response::nameserver::Nameserver (line 77) ... ok [INFO] [stdout] test src/response/nameserver.rs - response::nameserver::Nameserver::builder (line 147) ... ok [INFO] [stdout] test src/response/network.rs - response::network::Network::builder (line 206) ... ok [INFO] [stdout] test src/response/nameserver.rs - response::nameserver::Nameserver::new (line 147) ... ok [INFO] [stdout] test src/response/types.rs - response::types::ExtensionId (line 51) ... ok [INFO] [stdout] test src/response/types.rs - response::types::ExtensionId (line 59) ... ok [INFO] [stdout] test src/response/types.rs - response::types::Event (line 501) ... ok [INFO] [stdout] test src/response/types.rs - response::types::ExtensionId (line 40) ... ok [INFO] [stdout] test src/response/network.rs - response::network::Network::new (line 206) ... ok [INFO] [stdout] test src/response/types.rs - response::types::PublicId (line 617) ... ok [INFO] [stdout] test src/response/types.rs - response::types::Link (line 139) ... ok [INFO] [stdout] test src/response/types.rs - response::types::NoticeOrRemark (line 322) ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 44 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 9.93s [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "35fbbae191f389ba153a8be2a67568b8305fa01b375e9164aed796168f019dad", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "35fbbae191f389ba153a8be2a67568b8305fa01b375e9164aed796168f019dad", kill_on_drop: false }` [INFO] [stdout] 35fbbae191f389ba153a8be2a67568b8305fa01b375e9164aed796168f019dad