[INFO] fetching crate ruma-api 0.20.1... [INFO] building ruma-api-0.20.1 against try#d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6 for pr-146237-1 [INFO] extracting crate ruma-api 0.20.1 into /workspace/builds/worker-2-tc2/source [INFO] started tweaking crates.io crate ruma-api 0.20.1 [INFO] finished tweaking crates.io crate ruma-api 0.20.1 [INFO] tweaked toml for crates.io crate ruma-api 0.20.1 written to /workspace/builds/worker-2-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate ruma-api 0.20.1 on toolchain d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "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" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Locking 87 packages to latest compatible versions [INFO] [stderr] Adding http v0.2.12 (available: v1.3.1) [INFO] [stderr] Adding ruma-events v0.26.1 (available: v0.31.0) [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" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 739477b830154fe64192444b3b5f51cdf90725418cf717e91782fc4fa3e2438e [INFO] running `Command { std: "docker" "start" "-a" "739477b830154fe64192444b3b5f51cdf90725418cf717e91782fc4fa3e2438e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "739477b830154fe64192444b3b5f51cdf90725418cf717e91782fc4fa3e2438e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "739477b830154fe64192444b3b5f51cdf90725418cf717e91782fc4fa3e2438e", kill_on_drop: false }` [INFO] [stdout] 739477b830154fe64192444b3b5f51cdf90725418cf717e91782fc4fa3e2438e [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] ce44aa9404401a510b08e36ab36d3145a1f363cde446f8cea2bcdc3043e3a356 [INFO] running `Command { std: "docker" "start" "-a" "ce44aa9404401a510b08e36ab36d3145a1f363cde446f8cea2bcdc3043e3a356", kill_on_drop: false }` [INFO] [stderr] Compiling equivalent v1.0.2 [INFO] [stderr] Compiling hashbrown v0.16.0 [INFO] [stderr] Compiling winnow v0.5.40 [INFO] [stderr] Compiling serde_json v1.0.145 [INFO] [stderr] Compiling tracing-attributes v0.1.30 [INFO] [stderr] Compiling serde v1.0.228 [INFO] [stderr] Compiling indexmap v2.11.4 [INFO] [stderr] Compiling url v2.5.7 [INFO] [stderr] Compiling js_int v0.2.2 [INFO] [stderr] Compiling toml_edit v0.19.15 [INFO] [stderr] Compiling ruma-identifiers-validation v0.7.0 [INFO] [stderr] Compiling tracing v0.1.41 [INFO] [stderr] Compiling ruma-identifiers-macros v0.22.1 [INFO] [stderr] Compiling proc-macro-crate v1.3.1 [INFO] [stderr] Compiling ruma-serde-macros v0.6.1 [INFO] [stderr] Compiling ruma-api-macros v0.20.1 [INFO] [stderr] Compiling ruma-serde v0.6.1 [INFO] [stderr] Compiling ruma-identifiers v0.22.1 [INFO] [stderr] Compiling ruma-api v0.20.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> src/error.rs:239:16 [INFO] [stdout] | [INFO] [stdout] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> src/metadata.rs:77:16 [INFO] [stdout] | [INFO] [stdout] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 12.12s [INFO] running `Command { std: "docker" "inspect" "ce44aa9404401a510b08e36ab36d3145a1f363cde446f8cea2bcdc3043e3a356", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "ce44aa9404401a510b08e36ab36d3145a1f363cde446f8cea2bcdc3043e3a356", kill_on_drop: false }` [INFO] [stdout] ce44aa9404401a510b08e36ab36d3145a1f363cde446f8cea2bcdc3043e3a356 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+d79d87d4c0f7f0d0785ad6e493cf8cf718ed89a6" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] d6e8436d2f18e98ed692b38c0ffe7b83767848a69dbeb97cfab9dddcf1a004bf [INFO] running `Command { std: "docker" "start" "-a" "d6e8436d2f18e98ed692b38c0ffe7b83767848a69dbeb97cfab9dddcf1a004bf", kill_on_drop: false }` [INFO] [stderr] Compiling indexmap v1.9.3 [INFO] [stderr] Compiling target-triple v0.1.4 [INFO] [stderr] Compiling winnow v0.7.13 [INFO] [stderr] Compiling serde_spanned v1.0.2 [INFO] [stderr] Compiling toml_datetime v0.7.2 [INFO] [stderr] Compiling wildmatch v2.5.0 [INFO] [stderr] Compiling toml_writer v1.0.3 [INFO] [stderr] Compiling glob v0.3.3 [INFO] [stderr] Compiling indoc v1.0.9 [INFO] [stderr] Compiling ruma-events-macros v0.26.1 [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> src/error.rs:239:16 [INFO] [stdout] | [INFO] [stdout] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> src/metadata.rs:77:16 [INFO] [stdout] | [INFO] [stdout] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling ruma-common v0.8.0 [INFO] [stderr] Compiling toml_parser v1.0.3 [INFO] [stderr] Compiling toml v0.9.7 [INFO] [stderr] Compiling ruma-events v0.26.1 [INFO] [stderr] Compiling trybuild v1.0.111 [INFO] [stderr] Compiling ruma-api v0.20.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/no_fields.rs:4:5 [INFO] [stdout] | [INFO] [stdout] 4 | / ruma_api::ruma_api! { [INFO] [stdout] 5 | | metadata: { [INFO] [stdout] 6 | | description: "Does something.", [INFO] [stdout] 7 | | method: GET, [INFO] [stdout] ... | [INFO] [stdout] 15 | | response: {} [INFO] [stdout] 16 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api::ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api::ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ruma_api::ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/no_fields.rs:20:5 [INFO] [stdout] | [INFO] [stdout] 20 | / ruma_api::ruma_api! { [INFO] [stdout] 21 | | metadata: { [INFO] [stdout] 22 | | description: "Does something.", [INFO] [stdout] 23 | | method: POST, [INFO] [stdout] ... | [INFO] [stdout] 31 | | response: {} [INFO] [stdout] 32 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api::ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api::ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api::ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/optional_headers.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / ruma_api! { [INFO] [stdout] 4 | | metadata: { [INFO] [stdout] 5 | | description: "Does something.", [INFO] [stdout] 6 | | method: GET, [INFO] [stdout] ... | [INFO] [stdout] 22 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/header_override.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / ruma_api! { [INFO] [stdout] 9 | | metadata: { [INFO] [stdout] 10 | | description: "Does something.", [INFO] [stdout] 11 | | method: GET, [INFO] [stdout] ... | [INFO] [stdout] 30 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/path_arg_ordering.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / ruma_api! { [INFO] [stdout] 4 | | metadata: { [INFO] [stdout] 5 | | description: "Does something.", [INFO] [stdout] 6 | | method: GET, [INFO] [stdout] ... | [INFO] [stdout] 24 | | response: {} [INFO] [stdout] 25 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_macros.rs:9:5 [INFO] [stdout] | [INFO] [stdout] 9 | / ruma_api! { [INFO] [stdout] 10 | | metadata: { [INFO] [stdout] 11 | | description: "Does something.", [INFO] [stdout] 12 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stdout] ... | [INFO] [stdout] 55 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_macros.rs:66:5 [INFO] [stdout] | [INFO] [stdout] 66 | / ruma_api! { [INFO] [stdout] 67 | | metadata: { [INFO] [stdout] 68 | | description: "Does something.", [INFO] [stdout] 69 | | method: PUT, [INFO] [stdout] ... | [INFO] [stdout] 85 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_macros.rs:96:5 [INFO] [stdout] | [INFO] [stdout] 96 | / ruma_api! { [INFO] [stdout] 97 | | metadata: { [INFO] [stdout] 98 | | description: "Does something.", [INFO] [stdout] 99 | | method: PUT, [INFO] [stdout] ... | [INFO] [stdout] 115 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_macros.rs:121:5 [INFO] [stdout] | [INFO] [stdout] 121 | / ruma_api! { [INFO] [stdout] 122 | | metadata: { [INFO] [stdout] 123 | | description: "Does something.", [INFO] [stdout] 124 | | method: GET, [INFO] [stdout] ... | [INFO] [stdout] 136 | | response: {} [INFO] [stdout] 137 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/conversions.rs:9:1 [INFO] [stdout] | [INFO] [stdout] 9 | / ruma_api! { [INFO] [stdout] 10 | | metadata: { [INFO] [stdout] 11 | | description: "Does something.", [INFO] [stdout] 12 | | method: POST, [INFO] [stdout] ... | [INFO] [stdout] 40 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/conversions.rs:124:5 [INFO] [stdout] | [INFO] [stdout] 124 | / ruma_api! { [INFO] [stdout] 125 | | metadata: { [INFO] [stdout] 126 | | description: "Does something without query.", [INFO] [stdout] 127 | | method: POST, [INFO] [stdout] ... | [INFO] [stdout] 151 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_lifetime.rs:13:5 [INFO] [stdout] | [INFO] [stdout] 13 | / ruma_api! { [INFO] [stdout] 14 | | metadata: { [INFO] [stdout] 15 | | description: "Add an alias to a room.", [INFO] [stdout] 16 | | method: PUT, [INFO] [stdout] ... | [INFO] [stdout] 32 | | response: {} [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_lifetime.rs:40:5 [INFO] [stdout] | [INFO] [stdout] 40 | / ruma_api! { [INFO] [stdout] 41 | | metadata: { [INFO] [stdout] 42 | | description: "Add an alias to a room.", [INFO] [stdout] 43 | | method: PUT, [INFO] [stdout] ... | [INFO] [stdout] 58 | | response: {} [INFO] [stdout] 59 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_lifetime.rs:67:5 [INFO] [stdout] | [INFO] [stdout] 67 | / ruma_api! { [INFO] [stdout] 68 | | metadata: { [INFO] [stdout] 69 | | description: "Does something.", [INFO] [stdout] 70 | | method: POST, [INFO] [stdout] ... | [INFO] [stdout] 93 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_lifetime.rs:99:5 [INFO] [stdout] | [INFO] [stdout] 99 | / ruma_api! { [INFO] [stdout] 100 | | metadata: { [INFO] [stdout] 101 | | description: "Does something.", [INFO] [stdout] 102 | | method: GET, [INFO] [stdout] ... | [INFO] [stdout] 125 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> tests/ruma_api_lifetime.rs:131:5 [INFO] [stdout] | [INFO] [stdout] 131 | / ruma_api! { [INFO] [stdout] 132 | | metadata: { [INFO] [stdout] 133 | | description: "Get the list of rooms in this homeserver's public directory.", [INFO] [stdout] 134 | | method: GET, [INFO] [stdout] ... | [INFO] [stdout] 160 | | response: {} [INFO] [stdout] 161 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ruma_api` may come from an old version of the `ruma_api_macros` crate, try updating your dependency with `cargo update -p ruma_api_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> src/error.rs:239:16 [INFO] [stdout] | [INFO] [stdout] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stdout] --> src/metadata.rs:77:16 [INFO] [stdout] | [INFO] [stdout] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stdout] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 20.83s [INFO] running `Command { std: "docker" "inspect" "d6e8436d2f18e98ed692b38c0ffe7b83767848a69dbeb97cfab9dddcf1a004bf", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "d6e8436d2f18e98ed692b38c0ffe7b83767848a69dbeb97cfab9dddcf1a004bf", kill_on_drop: false }` [INFO] [stdout] d6e8436d2f18e98ed692b38c0ffe7b83767848a69dbeb97cfab9dddcf1a004bf