chris/ruwuma
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update expected stderr on tests for Rust 1.54

Browse Source
This commit is contained in:
Adam 2021-08-02 21:46:01 +02:00 committed by GitHub
parent 2bd2d18db9
commit e3427ba5d0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
crates/ruma-events/tests/ui/02-no-event-type.stderr
View File

@ -4,4 +4,4 @@ error: no event type attribute found, add `#[ruma_event(type = "any.room.event",
4 | #[derive(Clone, Debug, Deserialize, Serialize, EventContent)]
| ^^^^^^^^^^^^
|
= note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the derive macro `EventContent` (in Nightly builds, run with -Z macro-backtrace for more info)

2
crates/ruma-events/tests/ui/03-invalid-event-type.stderr
View File

@ -4,7 +4,7 @@ error: no event type attribute found, add `#[ruma_event(type = "any.room.event",
4 | #[derive(Clone, Debug, Deserialize, Serialize, EventContent)]
| ^^^^^^^^^^^^
|
= note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the derive macro `EventContent` (in Nightly builds, run with -Z macro-backtrace for more info)
error: expected one of: `type`, `kind`, `skip_redaction`, `custom_redacted`
--> $DIR/03-invalid-event-type.rs:11:14

2
crates/ruma-events/tests/ui/06-no-content-field.stderr
View File

@ -4,4 +4,4 @@ error: struct must contain a `content` field
5 | #[derive(Clone, Debug, Event)]
| ^^^^^
|
= note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the derive macro `Event` (in Nightly builds, run with -Z macro-backtrace for more info)

16
crates/ruma-identifiers/tests/ui/02-invalid-id-macros.stderr
View File

@ -5,7 +5,7 @@ error: proc macro panicked
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: message: Invalid event id
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the macro `ruma_identifiers::event_id` (in Nightly builds, run with -Z macro-backtrace for more info)
error: proc macro panicked
--> $DIR/02-invalid-id-macros.rs:3:13
@ -14,7 +14,7 @@ error: proc macro panicked
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: message: Invalid event id
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the macro `ruma_identifiers::event_id` (in Nightly builds, run with -Z macro-backtrace for more info)
error: proc macro panicked
--> $DIR/02-invalid-id-macros.rs:4:13
@ -23,7 +23,7 @@ error: proc macro panicked
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: message: Invalid mxc://
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the macro `ruma_identifiers::mxc_uri` (in Nightly builds, run with -Z macro-backtrace for more info)
error: proc macro panicked
--> $DIR/02-invalid-id-macros.rs:5:13
@ -32,7 +32,7 @@ error: proc macro panicked
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: message: Invalid room_alias_id
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the macro `ruma_identifiers::room_alias_id` (in Nightly builds, run with -Z macro-backtrace for more info)
error: proc macro panicked
--> $DIR/02-invalid-id-macros.rs:6:13
@ -41,7 +41,7 @@ error: proc macro panicked
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: message: Invalid room_id
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the macro `ruma_identifiers::room_id` (in Nightly builds, run with -Z macro-backtrace for more info)
error: proc macro panicked
--> $DIR/02-invalid-id-macros.rs:7:13
@ -50,7 +50,7 @@ error: proc macro panicked
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: message: Invalid room_version_id
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the macro `ruma_identifiers::room_version_id` (in Nightly builds, run with -Z macro-backtrace for more info)
error: proc macro panicked
--> $DIR/02-invalid-id-macros.rs:8:13
@ -59,7 +59,7 @@ error: proc macro panicked
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: message: Invalid server_name
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the macro `ruma_identifiers::server_name` (in Nightly builds, run with -Z macro-backtrace for more info)
error: proc macro panicked
--> $DIR/02-invalid-id-macros.rs:9:13
@ -68,4 +68,4 @@ error: proc macro panicked
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: message: Invalid user_id
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
= note: this error originates in the macro `ruma_identifiers::user_id` (in Nightly builds, run with -Z macro-backtrace for more info)