[INFO] fetching crate ruma-api 0.20.1... [INFO] testing ruma-api-0.20.1 against try#2440211fe03bc45c89b6dc1a3df18382ce91e32b for pr-146098-1 [INFO] extracting crate ruma-api 0.20.1 into /workspace/builds/worker-6-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-6-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate ruma-api 0.20.1 on toolchain 2440211fe03bc45c89b6dc1a3df18382ce91e32b [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [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.17) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] cdf8bdbdc8cec838c018510f180bb4343b6e699663153a19ce8a884b772a4cda [INFO] running `Command { std: "docker" "start" "-a" "cdf8bdbdc8cec838c018510f180bb4343b6e699663153a19ce8a884b772a4cda", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "cdf8bdbdc8cec838c018510f180bb4343b6e699663153a19ce8a884b772a4cda", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "cdf8bdbdc8cec838c018510f180bb4343b6e699663153a19ce8a884b772a4cda", kill_on_drop: false }` [INFO] [stdout] cdf8bdbdc8cec838c018510f180bb4343b6e699663153a19ce8a884b772a4cda [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 49bbb60a98ceb8b93fef9632614066df963f8442c357920c06da2bbbaa1b8847 [INFO] running `Command { std: "docker" "start" "-a" "49bbb60a98ceb8b93fef9632614066df963f8442c357920c06da2bbbaa1b8847", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro-crate v1.3.1 [INFO] [stderr] Compiling serde_json v1.0.145 [INFO] [stderr] Compiling serde v1.0.228 [INFO] [stderr] Compiling ruma-serde-macros v0.6.1 [INFO] [stderr] Compiling ruma-api-macros v0.20.1 [INFO] [stderr] Compiling url v2.5.7 [INFO] [stderr] Compiling js_int v0.2.2 [INFO] [stderr] Compiling ruma-identifiers-validation v0.7.0 [INFO] [stderr] Compiling ruma-serde v0.6.1 [INFO] [stderr] Compiling ruma-identifiers-macros v0.22.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 4.88s [INFO] running `Command { std: "docker" "inspect" "49bbb60a98ceb8b93fef9632614066df963f8442c357920c06da2bbbaa1b8847", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "49bbb60a98ceb8b93fef9632614066df963f8442c357920c06da2bbbaa1b8847", kill_on_drop: false }` [INFO] [stdout] 49bbb60a98ceb8b93fef9632614066df963f8442c357920c06da2bbbaa1b8847 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] da745b6446ebe8024ddadf7734d2da369c3a44b0c6604c613c970ab1ccf0aa26 [INFO] running `Command { std: "docker" "start" "-a" "da745b6446ebe8024ddadf7734d2da369c3a44b0c6604c613c970ab1ccf0aa26", kill_on_drop: false }` [INFO] [stderr] Compiling indexmap v1.9.3 [INFO] [stderr] Compiling winnow v0.7.13 [INFO] [stderr] Compiling target-triple v0.1.4 [INFO] [stderr] Compiling toml_datetime v0.7.2 [INFO] [stderr] Compiling serde_spanned v1.0.2 [INFO] [stderr] Compiling wildmatch v2.5.0 [INFO] [stderr] Compiling toml_writer v1.0.3 [INFO] [stderr] Compiling ruma-events-macros v0.26.1 [INFO] [stderr] Compiling glob v0.3.3 [INFO] [stderr] Compiling indoc v1.0.9 [INFO] [stderr] Compiling matches v0.1.10 [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 ruma-events v0.26.1 [INFO] [stderr] Compiling toml v0.9.7 [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/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/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] --> 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] [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] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 18.78s [INFO] running `Command { std: "docker" "inspect" "da745b6446ebe8024ddadf7734d2da369c3a44b0c6604c613c970ab1ccf0aa26", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "da745b6446ebe8024ddadf7734d2da369c3a44b0c6604c613c970ab1ccf0aa26", kill_on_drop: false }` [INFO] [stdout] da745b6446ebe8024ddadf7734d2da369c3a44b0c6604c613c970ab1ccf0aa26 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=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" "+2440211fe03bc45c89b6dc1a3df18382ce91e32b" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] 449f0ede14ee52911ef58988ab314a9401ac0aa3536230c960152db3c5769977 [INFO] running `Command { std: "docker" "start" "-a" "449f0ede14ee52911ef58988ab314a9401ac0aa3536230c960152db3c5769977", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> src/error.rs:239:16 [INFO] [stderr] | [INFO] [stderr] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> src/metadata.rs:77:16 [INFO] [stderr] | [INFO] [stderr] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: `ruma-api` (lib) generated 2 warnings [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/no_fields.rs:4:5 [INFO] [stderr] | [INFO] [stderr] 4 | / ruma_api::ruma_api! { [INFO] [stderr] 5 | | metadata: { [INFO] [stderr] 6 | | description: "Does something.", [INFO] [stderr] 7 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 15 | | response: {} [INFO] [stderr] 16 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api::ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api::ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/no_fields.rs:20:5 [INFO] [stderr] | [INFO] [stderr] 20 | / ruma_api::ruma_api! { [INFO] [stderr] 21 | | metadata: { [INFO] [stderr] 22 | | description: "Does something.", [INFO] [stderr] 23 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 31 | | response: {} [INFO] [stderr] 32 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api::ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api::ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `ruma-api` (test "no_fields") generated 2 warnings [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/conversions.rs:9:1 [INFO] [stderr] | [INFO] [stderr] 9 | / ruma_api! { [INFO] [stderr] 10 | | metadata: { [INFO] [stderr] 11 | | description: "Does something.", [INFO] [stderr] 12 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 40 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/conversions.rs:124:5 [INFO] [stderr] | [INFO] [stderr] 124 | / ruma_api! { [INFO] [stderr] 125 | | metadata: { [INFO] [stderr] 126 | | description: "Does something without query.", [INFO] [stderr] 127 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 151 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `ruma-api` (test "conversions") generated 2 warnings [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/path_arg_ordering.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "Does something.", [INFO] [stderr] 6 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 24 | | response: {} [INFO] [stderr] 25 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `ruma-api` (test "path_arg_ordering") generated 1 warning [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_lifetime.rs:13:5 [INFO] [stderr] | [INFO] [stderr] 13 | / ruma_api! { [INFO] [stderr] 14 | | metadata: { [INFO] [stderr] 15 | | description: "Add an alias to a room.", [INFO] [stderr] 16 | | method: PUT, [INFO] [stderr] ... | [INFO] [stderr] 32 | | response: {} [INFO] [stderr] 33 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_lifetime.rs:40:5 [INFO] [stderr] | [INFO] [stderr] 40 | / ruma_api! { [INFO] [stderr] 41 | | metadata: { [INFO] [stderr] 42 | | description: "Add an alias to a room.", [INFO] [stderr] 43 | | method: PUT, [INFO] [stderr] ... | [INFO] [stderr] 58 | | response: {} [INFO] [stderr] 59 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_lifetime.rs:67:5 [INFO] [stderr] | [INFO] [stderr] 67 | / ruma_api! { [INFO] [stderr] 68 | | metadata: { [INFO] [stderr] 69 | | description: "Does something.", [INFO] [stderr] 70 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 93 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_lifetime.rs:99:5 [INFO] [stderr] | [INFO] [stderr] 99 | / ruma_api! { [INFO] [stderr] 100 | | metadata: { [INFO] [stderr] 101 | | description: "Does something.", [INFO] [stderr] 102 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 125 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_lifetime.rs:131:5 [INFO] [stderr] | [INFO] [stderr] 131 | / ruma_api! { [INFO] [stderr] 132 | | metadata: { [INFO] [stderr] 133 | | description: "Get the list of rooms in this homeserver's public directory.", [INFO] [stderr] 134 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 160 | | response: {} [INFO] [stderr] 161 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `ruma-api` (test "ruma_api_lifetime") generated 5 warnings [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/optional_headers.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "Does something.", [INFO] [stderr] 6 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 22 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_macros.rs:9:5 [INFO] [stderr] | [INFO] [stderr] 9 | / ruma_api! { [INFO] [stderr] 10 | | metadata: { [INFO] [stderr] 11 | | description: "Does something.", [INFO] [stderr] 12 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stderr] ... | [INFO] [stderr] 55 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_macros.rs:66:5 [INFO] [stderr] | [INFO] [stderr] 66 | / ruma_api! { [INFO] [stderr] 67 | | metadata: { [INFO] [stderr] 68 | | description: "Does something.", [INFO] [stderr] 69 | | method: PUT, [INFO] [stderr] ... | [INFO] [stderr] 85 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_macros.rs:96:5 [INFO] [stderr] | [INFO] [stderr] 96 | / ruma_api! { [INFO] [stderr] 97 | | metadata: { [INFO] [stderr] 98 | | description: "Does something.", [INFO] [stderr] 99 | | method: PUT, [INFO] [stderr] ... | [INFO] [stderr] 115 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ruma_api_macros.rs:121:5 [INFO] [stderr] | [INFO] [stderr] 121 | / ruma_api! { [INFO] [stderr] 122 | | metadata: { [INFO] [stderr] 123 | | description: "Does something.", [INFO] [stderr] 124 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 136 | | response: {} [INFO] [stderr] 137 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/header_override.rs:8:1 [INFO] [stderr] | [INFO] [stderr] 8 | / ruma_api! { [INFO] [stderr] 9 | | metadata: { [INFO] [stderr] 10 | | description: "Does something.", [INFO] [stderr] 11 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 30 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `ruma-api` (test "optional_headers") generated 1 warning [INFO] [stderr] warning: `ruma-api` (test "ruma_api_macros") generated 4 warnings [INFO] [stderr] warning: `ruma-api` (test "header_override") generated 1 warning [INFO] [stderr] warning: `ruma-api` (lib test) generated 2 warnings (2 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.20s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ruma_api-4424a519d2dea0f1) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running tests/conversions.rs (/opt/rustwide/target/debug/deps/conversions-dbccd665ae99f97b) [INFO] [stdout] [INFO] [stdout] running 4 tests [INFO] [stdout] test request_with_user_id_serde ... ok [INFO] [stdout] test request_serde ... ok [INFO] [stdout] test without_query::request_without_query_with_user_id_serde ... ok [INFO] [stdout] test invalid_uri_should_not_panic ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s [INFO] [stdout] [INFO] [stderr] Running tests/header_override.rs (/opt/rustwide/target/debug/deps/header_override-373ddf7a5dc42b0d) [INFO] [stdout] [INFO] [stdout] running 2 tests [INFO] [stdout] test response_content_type_override ... ok [INFO] [stdout] test request_content_type_override ... ok [INFO] [stderr] Running tests/manual_endpoint_impl.rs (/opt/rustwide/target/debug/deps/manual_endpoint_impl-887ab33334f0a32d) [INFO] [stdout] [INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stderr] Running tests/no_fields.rs (/opt/rustwide/target/debug/deps/no_fields-e35a6bcb511bc7ff) [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 4 tests [INFO] [stdout] test empty_post_request_http_repr ... ok [INFO] [stdout] test empty_post_response_http_repr ... ok [INFO] [stdout] test empty_get_request_http_repr ... ok [INFO] [stdout] test empty_get_response_http_repr ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running tests/optional_headers.rs (/opt/rustwide/target/debug/deps/optional_headers-7845b32379b24b62) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running tests/path_arg_ordering.rs (/opt/rustwide/target/debug/deps/path_arg_ordering-5b52a2af9a090aaf) [INFO] [stdout] [INFO] [stdout] running 1 test [INFO] [stdout] test path_ordering_is_correct ... ok [INFO] [stderr] Running tests/ruma_api.rs (/opt/rustwide/target/debug/deps/ruma_api-0665a09b6aeee701) [INFO] [stdout] [INFO] [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 1 test [INFO] [stderr] Compiling proc-macro2 v1.0.101 [INFO] [stderr] Compiling quote v1.0.41 [INFO] [stderr] Compiling unicode-ident v1.0.19 [INFO] [stderr] Compiling serde_core v1.0.228 [INFO] [stderr] Compiling icu_normalizer_data v2.0.0 [INFO] [stderr] Compiling icu_properties_data v2.0.1 [INFO] [stderr] Compiling stable_deref_trait v1.2.0 [INFO] [stderr] Compiling serde v1.0.228 [INFO] [stderr] Compiling writeable v0.6.1 [INFO] [stderr] Compiling litemap v0.8.0 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling equivalent v1.0.2 [INFO] [stderr] Compiling hashbrown v0.16.0 [INFO] [stderr] Compiling toml_datetime v0.6.11 [INFO] [stderr] Compiling winnow v0.5.40 [INFO] [stderr] Compiling smallvec v1.15.1 [INFO] [stderr] Compiling once_cell v1.21.3 [INFO] [stderr] Compiling percent-encoding v2.3.2 [INFO] [stderr] Compiling utf8_iter v1.0.4 [INFO] [stderr] Compiling form_urlencoded v1.2.2 [INFO] [stderr] Compiling itoa v1.0.15 [INFO] [stderr] Compiling serde_json v1.0.145 [INFO] [stderr] Compiling ryu v1.0.20 [INFO] [stderr] Compiling memchr v2.7.6 [INFO] [stderr] Compiling bytes v1.10.1 [INFO] [stderr] Compiling base64 v0.13.1 [INFO] [stderr] Compiling autocfg v1.5.0 [INFO] [stderr] Compiling pin-project-lite v0.2.16 [INFO] [stderr] Compiling hashbrown v0.12.3 [INFO] [stderr] Compiling fnv v1.0.7 [INFO] [stderr] Compiling wildmatch v2.5.0 [INFO] [stderr] Compiling indoc v1.0.9 [INFO] [stderr] Compiling matches v0.1.10 [INFO] [stderr] Compiling tracing-core v0.1.34 [INFO] [stderr] Compiling indexmap v2.11.4 [INFO] [stderr] Compiling indexmap v1.9.3 [INFO] [stderr] Compiling syn v2.0.106 [INFO] [stderr] Compiling http v0.2.12 [INFO] [stderr] Compiling toml_edit v0.19.15 [INFO] [stderr] Compiling synstructure v0.13.2 [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-events-macros v0.26.1 [INFO] [stderr] Compiling zerofrom-derive v0.1.6 [INFO] [stderr] Compiling yoke-derive v0.8.0 [INFO] [stderr] Compiling zerovec-derive v0.11.1 [INFO] [stderr] Compiling displaydoc v0.2.5 [INFO] [stderr] Compiling serde_derive v1.0.228 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling tracing-attributes v0.1.30 [INFO] [stderr] Compiling zerofrom v0.1.6 [INFO] [stderr] Compiling yoke v0.8.0 [INFO] [stderr] Compiling zerovec v0.11.4 [INFO] [stderr] Compiling zerotrie v0.2.2 [INFO] [stderr] Compiling tracing v0.1.41 [INFO] [stderr] Compiling tinystr v0.8.1 [INFO] [stderr] Compiling potential_utf v0.1.3 [INFO] [stderr] Compiling icu_collections v2.0.0 [INFO] [stderr] Compiling icu_locale_core v2.0.0 [INFO] [stderr] Compiling icu_provider v2.0.0 [INFO] [stderr] Compiling js_int v0.2.2 [INFO] [stderr] Compiling icu_properties v2.0.1 [INFO] [stderr] Compiling icu_normalizer v2.0.0 [INFO] [stderr] Compiling ruma-serde v0.6.1 [INFO] [stderr] Compiling idna_adapter v1.2.1 [INFO] [stderr] Compiling idna v1.1.0 [INFO] [stderr] Compiling url v2.5.7 [INFO] [stderr] Compiling ruma-identifiers-validation v0.7.0 [INFO] [stderr] Compiling ruma-identifiers-macros v0.22.1 [INFO] [stderr] Compiling ruma-identifiers v0.22.1 [INFO] [stderr] Compiling ruma-common v0.8.0 [INFO] [stderr] Compiling ruma-api v0.20.1 (/opt/rustwide/workdir) [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/error.rs:239:16 [INFO] [stderr] | [INFO] [stderr] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/metadata.rs:77:16 [INFO] [stderr] | [INFO] [stderr] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: `ruma-api` (lib) generated 2 warnings [INFO] [stderr] Compiling ruma-events v0.26.1 [INFO] [stderr] Compiling ruma-api-tests v0.0.0 (/opt/rustwide/target/tests/trybuild/ruma-api) [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 47.74s [INFO] [stderr] [INFO] [stderr] [INFO] [stderr] test tests/ui/01-api-sanity-check.rs [should pass] ... ok [INFO] [stderr] [INFO] [stderr] WARNINGS: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ui/01-api-sanity-check.rs:5:1 [INFO] [stderr] | [INFO] [stderr] 5 | / ruma_api! { [INFO] [stderr] 6 | | metadata: { [INFO] [stderr] 7 | | description: "Does something.", [INFO] [stderr] 8 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stderr] ... | [INFO] [stderr] 56 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] STDERR: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/error.rs:239:16 [INFO] [stderr] | [INFO] [stderr] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/metadata.rs:77:16 [INFO] [stderr] | [INFO] [stderr] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/tests/ui/01-api-sanity-check.rs:5:1 [INFO] [stderr] | [INFO] [stderr] 5 | / ruma_api! { [INFO] [stderr] 6 | | metadata: { [INFO] [stderr] 7 | | description: "Does something.", [INFO] [stderr] 8 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stderr] ... | [INFO] [stderr] 56 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] test tests/ui/02-invalid-path.rs [should fail to compile] ... ok [INFO] [stderr] test tests/ui/03-move-value.rs [should pass] ... ok [INFO] [stderr] [INFO] [stderr] WARNINGS: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ui/03-move-value.rs:11:5 [INFO] [stderr] | [INFO] [stderr] 11 | / ruma_api! { [INFO] [stderr] 12 | | metadata: { [INFO] [stderr] 13 | | description: "Does something.", [INFO] [stderr] 14 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 42 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ui/03-move-value.rs:49:5 [INFO] [stderr] | [INFO] [stderr] 49 | / ruma_api! { [INFO] [stderr] 50 | | metadata: { [INFO] [stderr] 51 | | description: "Does something.", [INFO] [stderr] 52 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 80 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ui/03-move-value.rs:90:5 [INFO] [stderr] | [INFO] [stderr] 90 | / ruma_api! { [INFO] [stderr] 91 | | metadata: { [INFO] [stderr] 92 | | description: "Does something.", [INFO] [stderr] 93 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 119 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] STDERR: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/error.rs:239:16 [INFO] [stderr] | [INFO] [stderr] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/metadata.rs:77:16 [INFO] [stderr] | [INFO] [stderr] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/tests/ui/03-move-value.rs:11:5 [INFO] [stderr] | [INFO] [stderr] 11 | / ruma_api! { [INFO] [stderr] 12 | | metadata: { [INFO] [stderr] 13 | | description: "Does something.", [INFO] [stderr] 14 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 42 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/tests/ui/03-move-value.rs:49:5 [INFO] [stderr] | [INFO] [stderr] 49 | / ruma_api! { [INFO] [stderr] 50 | | metadata: { [INFO] [stderr] 51 | | description: "Does something.", [INFO] [stderr] 52 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 80 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/tests/ui/03-move-value.rs:90:5 [INFO] [stderr] | [INFO] [stderr] 90 | / ruma_api! { [INFO] [stderr] 91 | | metadata: { [INFO] [stderr] 92 | | description: "Does something.", [INFO] [stderr] 93 | | method: POST, [INFO] [stderr] ... | [INFO] [stderr] 119 | | } [INFO] [stderr] | |_____^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] test tests/ui/04-attributes.rs [should fail to compile] ... mismatch [INFO] [stderr] [INFO] [stderr] EXPECTED: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] error: cannot find attribute `not_a_real_attribute_should_fail` in this scope [INFO] [stderr] --> $DIR/04-attributes.rs:13:7 [INFO] [stderr] | [INFO] [stderr] 13 | #[not_a_real_attribute_should_fail] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] ACTUAL OUTPUT: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] error: cannot find attribute `not_a_real_attribute_should_fail` in this scope [INFO] [stderr] --> tests/ui/04-attributes.rs:13:7 [INFO] [stderr] | [INFO] [stderr] 13 | #[not_a_real_attribute_should_fail] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ui/04-attributes.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "Does something.", [INFO] [stderr] 6 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stderr] ... | [INFO] [stderr] 27 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] note: If the actual output is the correct output you can bless it by rerunning [INFO] [stderr] your test with the environment variable TRYBUILD=overwrite [INFO] [stderr] [INFO] [stderr] test tests/ui/05-request-only.rs [should pass] ... ok [INFO] [stderr] [INFO] [stderr] WARNINGS: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ui/05-request-only.rs:8:1 [INFO] [stderr] | [INFO] [stderr] 8 | / ruma_api! { [INFO] [stderr] 9 | | metadata: { [INFO] [stderr] 10 | | description: "Does something.", [INFO] [stderr] 11 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stderr] ... | [INFO] [stderr] 24 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] STDERR: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/error.rs:239:16 [INFO] [stderr] | [INFO] [stderr] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/metadata.rs:77:16 [INFO] [stderr] | [INFO] [stderr] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/tests/ui/05-request-only.rs:8:1 [INFO] [stderr] | [INFO] [stderr] 8 | / ruma_api! { [INFO] [stderr] 9 | | metadata: { [INFO] [stderr] 10 | | description: "Does something.", [INFO] [stderr] 11 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stderr] ... | [INFO] [stderr] 24 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] test tests/ui/06-response-only.rs [should pass] ... ok [INFO] [stderr] [INFO] [stderr] WARNINGS: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> tests/ui/06-response-only.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "Does something.", [INFO] [stderr] 6 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stderr] ... | [INFO] [stderr] 17 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] STDERR: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/error.rs:239:16 [INFO] [stderr] | [INFO] [stderr] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/src/metadata.rs:77:16 [INFO] [stderr] | [INFO] [stderr] 77 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `unstable-exhaustive-types` [INFO] [stderr] --> /opt/rustwide/workdir/tests/ui/06-response-only.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "Does something.", [INFO] [stderr] 6 | | method: POST, // An `http::Method` constant. No imports required. [INFO] [stderr] ... | [INFO] [stderr] 17 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `client`, `default`, and `server` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `ruma_api` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = 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] [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 macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] test tests/ui/07-error-type-attribute.rs [should fail to compile] ... ok [INFO] [stderr] test tests/ui/08-deprecated-without-added.rs [should fail to compile] ... mismatch [INFO] [stderr] [INFO] [stderr] EXPECTED: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] error: deprecated version is defined while added version is not defined [INFO] [stderr] --> tests/ui/08-deprecated-without-added.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "This will fail.", [INFO] [stderr] 6 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 20 | | response: {} [INFO] [stderr] 21 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: this error originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] ACTUAL OUTPUT: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] error: deprecated version is defined while added version is not defined [INFO] [stderr] --> tests/ui/08-deprecated-without-added.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "This will fail.", [INFO] [stderr] 6 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 20 | | response: {} [INFO] [stderr] 21 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: this error originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] note: If the actual output is the correct output you can bless it by rerunning [INFO] [stderr] your test with the environment variable TRYBUILD=overwrite [INFO] [stderr] [INFO] [stderr] test tests/ui/09-removed-without-deprecated.rs [should fail to compile] ... mismatch [INFO] [stderr] [INFO] [stderr] EXPECTED: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] error: removed version is defined while deprecated version is not defined [INFO] [stderr] --> tests/ui/09-removed-without-deprecated.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "This will fail.", [INFO] [stderr] 6 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 20 | | response: {} [INFO] [stderr] 21 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: this error originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] [INFO] [stderr] ACTUAL OUTPUT: [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] error: removed version is defined while deprecated version is not defined [INFO] [stderr] --> tests/ui/09-removed-without-deprecated.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | / ruma_api! { [INFO] [stderr] 4 | | metadata: { [INFO] [stderr] 5 | | description: "This will fail.", [INFO] [stderr] 6 | | method: GET, [INFO] [stderr] ... | [INFO] [stderr] 20 | | response: {} [INFO] [stderr] 21 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: this error originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ [INFO] [stderr] note: If the actual output is the correct output you can bless it by rerunning [INFO] [stderr] your test with the environment variable TRYBUILD=overwrite [INFO] [stderr] [INFO] [stderr] [INFO] [stderr] [INFO] [stdout] test ui ... FAILED [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] [INFO] [stdout] ---- ui stdout ---- [INFO] [stdout] [INFO] [stdout] thread 'ui' (43) panicked at /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/trybuild-1.0.111/src/run.rs:102:13: [INFO] [stdout] 3 of 9 tests failed [INFO] [stdout] stack backtrace: [INFO] [stdout] 0: 0x597d5b332ff2 - std::backtrace_rs::backtrace::libunwind::trace::h22a6a535a50603c6 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/../../backtrace/src/backtrace/libunwind.rs:117:9 [INFO] [stdout] 1: 0x597d5b332ff2 - std::backtrace_rs::backtrace::trace_unsynchronized::h2503a4f30dbfbaa2 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/../../backtrace/src/backtrace/mod.rs:66:14 [INFO] [stdout] 2: 0x597d5b332ff2 - std::sys::backtrace::_print_fmt::hec54e31f36456895 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/sys/backtrace.rs:66:9 [INFO] [stdout] 3: 0x597d5b332ff2 - ::fmt::hb1988e8b50fa5f19 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/sys/backtrace.rs:39:26 [INFO] [stdout] 4: 0x597d5b344c3f - core::fmt::rt::Argument::fmt::h3118a66e1a57a586 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/fmt/rt.rs:173:76 [INFO] [stdout] 5: 0x597d5b344c3f - core::fmt::write::hcd056e06a609f600 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/fmt/mod.rs:1468:25 [INFO] [stdout] 6: 0x597d5b2fcbc1 - std::io::default_write_fmt::hdabc5d6505cb374b [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/io/mod.rs:639:11 [INFO] [stdout] 7: 0x597d5b2fcbc1 - std::io::Write::write_fmt::h18c82179fdc1f9d2 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/io/mod.rs:1954:13 [INFO] [stdout] 8: 0x597d5b30a482 - std::sys::backtrace::BacktraceLock::print::h69f50ba7cfff8317 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/sys/backtrace.rs:42:9 [INFO] [stdout] 9: 0x597d5b30faff - std::panicking::default_hook::{{closure}}::hfa978eb2255ab3ab [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:301:27 [INFO] [stdout] 10: 0x597d5b30f991 - std::panicking::default_hook::h09da2eaf8f1deadd [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:325:9 [INFO] [stdout] 11: 0x597d5b2cd28e - as core::ops::function::Fn>::call::h1697e4d80f236ef6 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/alloc/src/boxed.rs:1987:9 [INFO] [stdout] 12: 0x597d5b2cd28e - test::test_main_with_exit_callback::{{closure}}::h8f63929ca9fd483b [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/test/src/lib.rs:145:21 [INFO] [stdout] 13: 0x597d5b3101bf - as core::ops::function::Fn>::call::hba67e0dc3e3fc548 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/alloc/src/boxed.rs:1987:9 [INFO] [stdout] 14: 0x597d5b3101bf - std::panicking::panic_with_hook::h13c40d280d130fd3 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:842:13 [INFO] [stdout] 15: 0x597d5b31001a - std::panicking::panic_handler::{{closure}}::hd79d22e8a1d3b951 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:707:13 [INFO] [stdout] 16: 0x597d5b30a5c9 - std::sys::backtrace::__rust_end_short_backtrace::h83414d1ec69cf3a6 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/sys/backtrace.rs:174:18 [INFO] [stdout] 17: 0x597d5b2f01cd - __rustc[b78aa6c7b08e5dc4]::rust_begin_unwind [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:698:5 [INFO] [stdout] 18: 0x597d5b34dfb0 - core::panicking::panic_fmt::h326b75cf8ee01b13 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/panicking.rs:78:14 [INFO] [stdout] 19: 0x597d5b109433 - trybuild::run::::run::h374b5840652dc904 [INFO] [stdout] at /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/trybuild-1.0.111/src/run.rs:102:13 [INFO] [stdout] 20: 0x597d5b103748 - ::drop::h00513535bea5a23e [INFO] [stdout] at /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/trybuild-1.0.111/src/lib.rs:342:38 [INFO] [stdout] 21: 0x597d5b06a757 - core::ptr::drop_in_place::hd4e21b2304cce6e2 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/ptr/mod.rs:804:1 [INFO] [stdout] 22: 0x597d5b06adb6 - ruma_api::ui::hd9c736a96adaf030 [INFO] [stdout] at /opt/rustwide/workdir/tests/ruma_api.rs:13:1 [INFO] [stdout] 23: 0x597d5b06ade7 - ruma_api::ui::{{closure}}::h4281be6882a71491 [INFO] [stdout] at /opt/rustwide/workdir/tests/ruma_api.rs:2:8 [INFO] [stdout] 24: 0x597d5b06a6b6 - core::ops::function::FnOnce::call_once::h639e9044aab28035 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 25: 0x597d5b2cd06b - core::ops::function::FnOnce::call_once::he420dad47d9aac14 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 26: 0x597d5b2cd06b - test::__rust_begin_short_backtrace::h51976f55c263f7c2 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/test/src/lib.rs:663:18 [INFO] [stdout] 27: 0x597d5b2e2c95 - test::run_test_in_process::{{closure}}::h6aa4339396d33320 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/test/src/lib.rs:686:74 [INFO] [stdout] 28: 0x597d5b2e2c95 - as core::ops::function::FnOnce<()>>::call_once::h5bd0ba3863a53529 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/panic/unwind_safe.rs:274:9 [INFO] [stdout] 29: 0x597d5b2e2c95 - std::panicking::catch_unwind::do_call::h5c710722c40c5839 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:590:40 [INFO] [stdout] 30: 0x597d5b2e2c95 - std::panicking::catch_unwind::hf41b5be070ce0f19 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:553:19 [INFO] [stdout] 31: 0x597d5b2e2c95 - std::panic::catch_unwind::h4559aa103e6f16d6 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panic.rs:359:14 [INFO] [stdout] 32: 0x597d5b2e2c95 - test::run_test_in_process::he6fd763a772ff213 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/test/src/lib.rs:686:27 [INFO] [stdout] 33: 0x597d5b2e2c95 - test::run_test::{{closure}}::he46f5435849feb5b [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/test/src/lib.rs:607:43 [INFO] [stdout] 34: 0x597d5b2b94a4 - test::run_test::{{closure}}::h12a66289c31b502a [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/test/src/lib.rs:637:41 [INFO] [stdout] 35: 0x597d5b2b94a4 - std::sys::backtrace::__rust_begin_short_backtrace::h614a7925ed7b2f5e [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/sys/backtrace.rs:158:18 [INFO] [stdout] 36: 0x597d5b2bce4a - std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::hbc654088c5dbff36 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/thread/mod.rs:559:17 [INFO] [stdout] 37: 0x597d5b2bce4a - as core::ops::function::FnOnce<()>>::call_once::h3f631d2ca531b61d [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/panic/unwind_safe.rs:274:9 [INFO] [stdout] 38: 0x597d5b2bce4a - std::panicking::catch_unwind::do_call::hd2548748db0aa717 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:590:40 [INFO] [stdout] 39: 0x597d5b2bce4a - std::panicking::catch_unwind::hf7d8620d84df48e2 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panicking.rs:553:19 [INFO] [stdout] 40: 0x597d5b2bce4a - std::panic::catch_unwind::hdde75b8543fcb96b [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/panic.rs:359:14 [INFO] [stdout] 41: 0x597d5b2bce4a - std::thread::Builder::spawn_unchecked_::{{closure}}::h991e7d03b432cf3f [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/thread/mod.rs:557:30 [INFO] [stdout] 42: 0x597d5b2bce4a - core::ops::function::FnOnce::call_once{{vtable.shim}}::hebddb40255441657 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 43: 0x597d5b304f7f - as core::ops::function::FnOnce>::call_once::h55e8930dc7db99a5 [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/alloc/src/boxed.rs:1973:9 [INFO] [stdout] 44: 0x597d5b304f7f - std::sys::thread::unix::Thread::new::thread_start::he23d038ee4fa004e [INFO] [stdout] at /rustc/2440211fe03bc45c89b6dc1a3df18382ce91e32b/library/std/src/sys/thread/unix.rs:126:17 [INFO] [stdout] 45: 0x760542d54aa4 - [INFO] [stdout] 46: 0x760542de1a34 - clone [INFO] [stdout] 47: 0x0 - [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] ui [INFO] [stdout] [INFO] [stdout] test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 53.22s [INFO] [stdout] [INFO] [stderr] error: test failed, to rerun pass `--test ruma_api` [INFO] running `Command { std: "docker" "inspect" "449f0ede14ee52911ef58988ab314a9401ac0aa3536230c960152db3c5769977", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "449f0ede14ee52911ef58988ab314a9401ac0aa3536230c960152db3c5769977", kill_on_drop: false }` [INFO] [stdout] 449f0ede14ee52911ef58988ab314a9401ac0aa3536230c960152db3c5769977