[INFO] fetching crate ruma-api 0.20.1...
[INFO] testing ruma-api-0.20.1 against 1.91.0 for beta-1.92-2
[INFO] extracting crate ruma-api 0.20.1 into /workspace/builds/worker-3-tc1/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-3-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate ruma-api 0.20.1 on toolchain 1.91.0
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.91.0" "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" "+1.91.0" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]      Locking 87 packages to latest compatible versions
[INFO] [stderr]       Adding http v0.2.12 (available: v1.3.1)
[INFO] [stderr]       Adding ruma-events v0.26.1 (available: v0.31.0)
[INFO] [stderr]       Adding thiserror v1.0.69 (available: v2.0.17)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.91.0" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded ruma-serde-macros v0.6.1
[INFO] [stderr]   Downloaded ruma-identifiers-macros v0.22.1
[INFO] [stderr]   Downloaded ruma-serde v0.6.1
[INFO] [stderr]   Downloaded indoc v1.0.9
[INFO] [stderr]   Downloaded ruma-api-macros v0.20.1
[INFO] [stderr]   Downloaded ruma-common v0.8.0
[INFO] [stderr]   Downloaded ruma-events-macros v0.26.1
[INFO] [stderr]   Downloaded ruma-identifiers v0.22.1
[INFO] [stderr]   Downloaded js_int v0.2.2
[INFO] [stderr]   Downloaded wildmatch v2.5.0
[INFO] [stderr]   Downloaded ruma-events v0.26.1
[INFO] [stderr]   Downloaded ruma-identifiers-validation v0.7.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+1.91.0" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 7df30fad5aff0648841a3b17c469e3de095df2e295f03566c6bceeb70cdb3195
[INFO] running `Command { std: "docker" "start" "-a" "7df30fad5aff0648841a3b17c469e3de095df2e295f03566c6bceeb70cdb3195", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "7df30fad5aff0648841a3b17c469e3de095df2e295f03566c6bceeb70cdb3195", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "7df30fad5aff0648841a3b17c469e3de095df2e295f03566c6bceeb70cdb3195", kill_on_drop: false }`
[INFO] [stdout] 7df30fad5aff0648841a3b17c469e3de095df2e295f03566c6bceeb70cdb3195
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+1.91.0" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] f2909c637d96ff24ac0319d7faec288eefb81aea09fa3a6ebde0907b75d5b578
[INFO] running `Command { std: "docker" "start" "-a" "f2909c637d96ff24ac0319d7faec288eefb81aea09fa3a6ebde0907b75d5b578", kill_on_drop: false }`
[INFO] [stderr]    Compiling hashbrown v0.16.0
[INFO] [stderr]    Compiling winnow v0.5.40
[INFO] [stderr]    Compiling serde_json v1.0.145
[INFO] [stderr]    Compiling tracing-attributes v0.1.30
[INFO] [stderr]    Compiling serde v1.0.228
[INFO] [stderr]    Compiling url v2.5.7
[INFO] [stderr]    Compiling js_int v0.2.2
[INFO] [stderr]    Compiling indexmap v2.12.0
[INFO] [stderr]    Compiling ruma-identifiers-validation v0.7.0
[INFO] [stderr]    Compiling tracing v0.1.41
[INFO] [stderr]    Compiling ruma-identifiers-macros v0.22.1
[INFO] [stderr]    Compiling toml_edit v0.19.15
[INFO] [stderr]    Compiling proc-macro-crate v1.3.1
[INFO] [stderr]    Compiling ruma-serde-macros v0.6.1
[INFO] [stderr]    Compiling ruma-api-macros v0.20.1
[INFO] [stderr]    Compiling ruma-serde v0.6.1
[INFO] [stderr]    Compiling ruma-identifiers v0.22.1
[INFO] [stderr]    Compiling ruma-api v0.20.1 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types`
[INFO] [stdout]    --> src/error.rs:239:16
[INFO] [stdout]     |
[INFO] [stdout] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)]
[INFO] [stdout]     |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `client`, `default`, and `server`
[INFO] [stdout]     = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 8.27s
[INFO] running `Command { std: "docker" "inspect" "f2909c637d96ff24ac0319d7faec288eefb81aea09fa3a6ebde0907b75d5b578", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f2909c637d96ff24ac0319d7faec288eefb81aea09fa3a6ebde0907b75d5b578", kill_on_drop: false }`
[INFO] [stdout] f2909c637d96ff24ac0319d7faec288eefb81aea09fa3a6ebde0907b75d5b578
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+1.91.0" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] ef5b1b7b8815286bde6bb63ea47f41a93a04601ad198a3450011641b9001fb61
[INFO] running `Command { std: "docker" "start" "-a" "ef5b1b7b8815286bde6bb63ea47f41a93a04601ad198a3450011641b9001fb61", kill_on_drop: false }`
[INFO] [stderr]    Compiling winnow v0.7.13
[INFO] [stderr]    Compiling target-triple v1.0.0
[INFO] [stderr]    Compiling indexmap v1.9.3
[INFO] [stderr]    Compiling toml_datetime v0.7.3
[INFO] [stderr]    Compiling serde_spanned v1.0.3
[INFO] [stderr]    Compiling toml_writer v1.0.4
[INFO] [stderr]    Compiling wildmatch v2.5.0
[INFO] [stderr]    Compiling indoc v1.0.9
[INFO] [stderr]    Compiling glob v0.3.3
[INFO] [stderr]    Compiling ruma-events-macros v0.26.1
[INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types`
[INFO] [stdout]    --> src/error.rs:239:16
[INFO] [stdout]     |
[INFO] [stdout] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)]
[INFO] [stdout]     |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `client`, `default`, and `server`
[INFO] [stdout]     = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling ruma-common v0.8.0
[INFO] [stderr]    Compiling ruma-events v0.26.1
[INFO] [stderr]    Compiling toml_parser v1.0.4
[INFO] [stderr]    Compiling toml v0.9.8
[INFO] [stderr]    Compiling trybuild v1.0.113
[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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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: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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `ruma_api` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `unstable-exhaustive-types`
[INFO] [stdout]    --> src/error.rs:239:16
[INFO] [stdout]     |
[INFO] [stdout] 239 | #[cfg_attr(not(feature = "unstable-exhaustive-types"), non_exhaustive)]
[INFO] [stdout]     |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `client`, `default`, and `server`
[INFO] [stdout]     = help: consider adding `unstable-exhaustive-types` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 11.73s
[INFO] running `Command { std: "docker" "inspect" "ef5b1b7b8815286bde6bb63ea47f41a93a04601ad198a3450011641b9001fb61", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "ef5b1b7b8815286bde6bb63ea47f41a93a04601ad198a3450011641b9001fb61", kill_on_drop: false }`
[INFO] [stdout] ef5b1b7b8815286bde6bb63ea47f41a93a04601ad198a3450011641b9001fb61
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+1.91.0" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] f5d1ad4a3fbc6305f1f79ef57d44250332facb7b6395f4973f7ce03ac958be9e
[INFO] running `Command { std: "docker" "start" "-a" "f5d1ad4a3fbc6305f1f79ef57d44250332facb7b6395f4973f7ce03ac958be9e", 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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: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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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: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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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: 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 "conversions") generated 2 warnings
[INFO] [stderr] warning: `ruma-api` (test "ruma_api_lifetime") generated 5 warnings
[INFO] [stderr] warning: `ruma-api` (test "ruma_api_macros") generated 4 warnings
[INFO] [stderr] warning: `ruma-api` (test "no_fields") generated 2 warnings
[INFO] [stderr] warning: `ruma-api` (lib test) generated 2 warnings (2 duplicates)
[INFO] [stderr] warning: `ruma-api` (test "path_arg_ordering") generated 1 warning
[INFO] [stderr] warning: `ruma-api` (test "optional_headers") generated 1 warning
[INFO] [stderr] warning: `ruma-api` (test "header_override") generated 1 warning
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.09s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ruma_api-6374f5ee74f88001)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stderr]      Running tests/conversions.rs (/opt/rustwide/target/debug/deps/conversions-dd00e2a434436f00)
[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 invalid_uri_should_not_panic ... ok
[INFO] [stdout] test request_serde ... ok
[INFO] [stdout] test without_query::request_without_query_with_user_id_serde ... ok
[INFO] [stdout] test request_with_user_id_serde ... 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/header_override.rs (/opt/rustwide/target/debug/deps/header_override-42b7e4f9520390b8)
[INFO] [stdout] 
[INFO] [stdout] running 2 tests
[INFO] [stdout] test request_content_type_override ... ok
[INFO] [stdout] test response_content_type_override ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/manual_endpoint_impl.rs (/opt/rustwide/target/debug/deps/manual_endpoint_impl-929251a08480db88)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stderr]      Running tests/no_fields.rs (/opt/rustwide/target/debug/deps/no_fields-3e6b5132edfb9377)
[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_get_request_http_repr ... ok
[INFO] [stdout] test empty_get_response_http_repr ... ok
[INFO] [stdout] test empty_post_request_http_repr ... ok
[INFO] [stdout] test empty_post_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-7fd69291b3ea09f2)
[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-b17e6d2eff501889)
[INFO] [stdout] 
[INFO] [stdout] running 1 test
[INFO] [stdout] test path_ordering_is_correct ... ok
[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] [stderr]      Running tests/ruma_api.rs (/opt/rustwide/target/debug/deps/ruma_api-5d0a46e3b0c4bee2)
[INFO] [stdout] 
[INFO] [stdout] running 1 test
[INFO] [stderr]    Compiling proc-macro2 v1.0.103
[INFO] [stderr]    Compiling unicode-ident v1.0.22
[INFO] [stderr]    Compiling quote v1.0.41
[INFO] [stderr]    Compiling serde_core v1.0.228
[INFO] [stderr]    Compiling icu_normalizer_data v2.1.1
[INFO] [stderr]    Compiling icu_properties_data v2.1.1
[INFO] [stderr]    Compiling stable_deref_trait v1.2.1
[INFO] [stderr]    Compiling serde v1.0.228
[INFO] [stderr]    Compiling litemap v0.8.1
[INFO] [stderr]    Compiling writeable v0.6.2
[INFO] [stderr]    Compiling thiserror v1.0.69
[INFO] [stderr]    Compiling equivalent v1.0.2
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling hashbrown v0.16.0
[INFO] [stderr]    Compiling winnow v0.5.40
[INFO] [stderr]    Compiling toml_datetime v0.6.11
[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 serde_json v1.0.145
[INFO] [stderr]    Compiling form_urlencoded v1.2.2
[INFO] [stderr]    Compiling itoa v1.0.15
[INFO] [stderr]    Compiling memchr v2.7.6
[INFO] [stderr]    Compiling ryu v1.0.20
[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.12.0
[INFO] [stderr]    Compiling indexmap v1.9.3
[INFO] [stderr]    Compiling http v0.2.12
[INFO] [stderr]    Compiling syn v2.0.108
[INFO] [stderr]    Compiling toml_edit v0.19.15
[INFO] [stderr]    Compiling proc-macro-crate v1.3.1
[INFO] [stderr]    Compiling synstructure v0.13.2
[INFO] [stderr]    Compiling ruma-serde-macros v0.6.1
[INFO] [stderr]    Compiling ruma-events-macros v0.26.1
[INFO] [stderr]    Compiling ruma-api-macros v0.20.1
[INFO] [stderr]    Compiling zerofrom-derive v0.1.6
[INFO] [stderr]    Compiling yoke-derive v0.8.1
[INFO] [stderr]    Compiling zerovec-derive v0.11.2
[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 tracing v0.1.41
[INFO] [stderr]    Compiling yoke v0.8.1
[INFO] [stderr]    Compiling zerovec v0.11.5
[INFO] [stderr]    Compiling zerotrie v0.2.3
[INFO] [stderr]    Compiling tinystr v0.8.2
[INFO] [stderr]    Compiling potential_utf v0.1.4
[INFO] [stderr]    Compiling icu_collections v2.1.1
[INFO] [stderr]    Compiling icu_locale_core v2.1.1
[INFO] [stderr]    Compiling icu_provider v2.1.1
[INFO] [stderr]    Compiling icu_normalizer v2.1.1
[INFO] [stderr]    Compiling icu_properties v2.1.1
[INFO] [stderr]    Compiling js_int v0.2.2
[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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 28.61s
[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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] [stderr] error: test failed, to rerun pass `--test ruma_api`
[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.113/src/run.rs:102:13:
[INFO] [stdout] 3 of 9 tests failed
[INFO] [stdout] stack backtrace:
[INFO] [stdout]    0:     0x5ef471b2b6c2 - std::backtrace_rs::backtrace::libunwind::trace::h62f3c6bea0fedab3
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/../../backtrace/src/backtrace/libunwind.rs:117:9
[INFO] [stdout]    1:     0x5ef471b2b6c2 - std::backtrace_rs::backtrace::trace_unsynchronized::hc41aaca6c0af0bde
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/../../backtrace/src/backtrace/mod.rs:66:14
[INFO] [stdout]    2:     0x5ef471b2b6c2 - std::sys::backtrace::_print_fmt::h33ac2b97007106cc
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/sys/backtrace.rs:66:9
[INFO] [stdout]    3:     0x5ef471b2b6c2 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h4e0a3aeea0f9c085
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/sys/backtrace.rs:39:26
[INFO] [stdout]    4:     0x5ef471b3d2bf - core::fmt::rt::Argument::fmt::h1edd6a3e00b22f10
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/fmt/rt.rs:173:76
[INFO] [stdout]    5:     0x5ef471b3d2bf - core::fmt::write::hecf68a131630c74d
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/fmt/mod.rs:1468:25
[INFO] [stdout]    6:     0x5ef471af58e1 - std::io::default_write_fmt::ha6b238eff7f0ef8a
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/io/mod.rs:639:11
[INFO] [stdout]    7:     0x5ef471af58e1 - std::io::Write::write_fmt::h9846fe3d2a36c1ea
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/io/mod.rs:1954:13
[INFO] [stdout]    8:     0x5ef471b03012 - std::sys::backtrace::BacktraceLock::print::h75160192768e5621
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/sys/backtrace.rs:42:9
[INFO] [stdout]    9:     0x5ef471b0867f - std::panicking::default_hook::{{closure}}::h14d82797cfb1ddcb
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:301:27
[INFO] [stdout]   10:     0x5ef471b08511 - std::panicking::default_hook::h63f9bf8161c5d325
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:325:9
[INFO] [stdout]   11:     0x5ef471ac5f8e - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::hb8126f8384f98101
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/alloc/src/boxed.rs:1999:9
[INFO] [stdout]   12:     0x5ef471ac5f8e - test::test_main_with_exit_callback::{{closure}}::hae96ae0cd2f2ce70
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/test/src/lib.rs:145:21
[INFO] [stdout]   13:     0x5ef471b08d3f - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::ha703f6686c81d0c6
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/alloc/src/boxed.rs:1999:9
[INFO] [stdout]   14:     0x5ef471b08d3f - std::panicking::panic_with_hook::h3173740e06bd0752
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:842:13
[INFO] [stdout]   15:     0x5ef471b08b9a - std::panicking::panic_handler::{{closure}}::hbac492c61eb56a87
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:707:13
[INFO] [stdout]   16:     0x5ef471b03159 - std::sys::backtrace::__rust_end_short_backtrace::haa3eac3df9535320
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/sys/backtrace.rs:174:18
[INFO] [stdout]   17:     0x5ef471ae8e4d - __rustc[de0091b922c53d7e]::rust_begin_unwind
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:698:5
[INFO] [stdout]   18:     0x5ef471b46630 - core::panicking::panic_fmt::h5138da2ef87be35b
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/panicking.rs:75:14
[INFO] [stdout]   19:     0x5ef4718f8583 - trybuild::run::<impl trybuild::Runner>::run::h4c476863394dee38
[INFO] [stdout]                                at /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/trybuild-1.0.113/src/run.rs:102:13
[INFO] [stdout]   20:     0x5ef4718f24c8 - <trybuild::TestCases as core::ops::drop::Drop>::drop::hc5b2fbc9389f46b4
[INFO] [stdout]                                at /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/trybuild-1.0.113/src/lib.rs:342:38
[INFO] [stdout]   21:     0x5ef471858e27 - core::ptr::drop_in_place<trybuild::TestCases>::hecc6015990748698
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/ptr/mod.rs:804:1
[INFO] [stdout]   22:     0x5ef471859486 - ruma_api::ui::h649d63ac09c2fd7d
[INFO] [stdout]                                at /opt/rustwide/workdir/tests/ruma_api.rs:13:1
[INFO] [stdout]   23:     0x5ef4718594b7 - ruma_api::ui::{{closure}}::h8d857bbeb38d6dce
[INFO] [stdout]                                at /opt/rustwide/workdir/tests/ruma_api.rs:2:8
[INFO] [stdout]   24:     0x5ef471858d96 - core::ops::function::FnOnce::call_once::he33ebe1373403030
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   25:     0x5ef471ac5d6b - core::ops::function::FnOnce::call_once::h8f50ae93d93b62b4
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   26:     0x5ef471ac5d6b - test::__rust_begin_short_backtrace::h447963718d05a644
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/test/src/lib.rs:663:18
[INFO] [stdout]   27:     0x5ef471adb9a5 - test::run_test_in_process::{{closure}}::hf890ba4755ca86c0
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/test/src/lib.rs:686:74
[INFO] [stdout]   28:     0x5ef471adb9a5 - <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::h31e4b2860e583faa
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/panic/unwind_safe.rs:274:9
[INFO] [stdout]   29:     0x5ef471adb9a5 - std::panicking::catch_unwind::do_call::hec7cdbbe797e2cab
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:590:40
[INFO] [stdout]   30:     0x5ef471adb9a5 - std::panicking::catch_unwind::h24d3b93458b5ba67
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:553:19
[INFO] [stdout]   31:     0x5ef471adb9a5 - std::panic::catch_unwind::h46eeec7cf9c9336c
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panic.rs:359:14
[INFO] [stdout]   32:     0x5ef471adb9a5 - test::run_test_in_process::h290de6e559006104
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/test/src/lib.rs:686:27
[INFO] [stdout]   33:     0x5ef471adb9a5 - test::run_test::{{closure}}::h26eeb2c5f7e9a995
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/test/src/lib.rs:607:43
[INFO] [stdout]   34:     0x5ef471ab21a4 - test::run_test::{{closure}}::h85af00882daabeaa
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/test/src/lib.rs:637:41
[INFO] [stdout]   35:     0x5ef471ab21a4 - std::sys::backtrace::__rust_begin_short_backtrace::h9d9305dda51fa5f2
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/sys/backtrace.rs:158:18
[INFO] [stdout]   36:     0x5ef471ab5b4a - std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::hc6aada8b43f0527b
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/thread/mod.rs:559:17
[INFO] [stdout]   37:     0x5ef471ab5b4a - <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::ha89fe5505c1206f5
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/panic/unwind_safe.rs:274:9
[INFO] [stdout]   38:     0x5ef471ab5b4a - std::panicking::catch_unwind::do_call::he3e0bef721d99583
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:590:40
[INFO] [stdout]   39:     0x5ef471ab5b4a - std::panicking::catch_unwind::ha8241964d3d773cd
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panicking.rs:553:19
[INFO] [stdout]   40:     0x5ef471ab5b4a - std::panic::catch_unwind::ha8554bc7696cae72
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/panic.rs:359:14
[INFO] [stdout]   41:     0x5ef471ab5b4a - std::thread::Builder::spawn_unchecked_::{{closure}}::he06f1f62b4c90f8d
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/thread/mod.rs:557:30
[INFO] [stdout]   42:     0x5ef471ab5b4a - core::ops::function::FnOnce::call_once{{vtable.shim}}::ha7fd20ecae19b9b9
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/core/src/ops/function.rs:250:5
[INFO] [stdout]   43:     0x5ef471afdbbf - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h43642ed9c40e0ab2
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/alloc/src/boxed.rs:1985:9
[INFO] [stdout]   44:     0x5ef471afdbbf - std::sys::thread::unix::Thread::new::thread_start::h38da0f633f090ce2
[INFO] [stdout]                                at /rustc/f8297e351a40c1439a467bbbb6879088047f50b3/library/std/src/sys/thread/unix.rs:126:17
[INFO] [stdout]   45:     0x7729b8d7aaa4 - <unknown>
[INFO] [stdout]   46:     0x7729b8e07a64 - clone
[INFO] [stdout]   47:                0x0 - <unknown>
[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 32.41s
[INFO] [stdout] 
[INFO] running `Command { std: "docker" "inspect" "f5d1ad4a3fbc6305f1f79ef57d44250332facb7b6395f4973f7ce03ac958be9e", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f5d1ad4a3fbc6305f1f79ef57d44250332facb7b6395f4973f7ce03ac958be9e", kill_on_drop: false }`
[INFO] [stdout] f5d1ad4a3fbc6305f1f79ef57d44250332facb7b6395f4973f7ce03ac958be9e
