hello! I'm trying to package the maud 0.27.0 crate into Debian, I noticed the following tests though - I'm not sure why this breaks, and it might be due to the versions of the other crates we have in Debian, but I was wondering if you have any hints/suggestions since you're more familiar with the codebase? :) Thank you!
test tests/warnings/attribute-missing-value.rs ... ok
test tests/warnings/class-shorthand-missing-value.rs ... ok
test tests/warnings/dynamic-attribute-names.rs ... ok
test tests/warnings/elements-in-attributes.rs ... ok
test tests/warnings/keyword-without-at.rs ... mismatch
EXPECTED:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: found keyword `if`
--> tests/warnings/keyword-without-at.rs:5:9
|
5 | if {}
| ^^
|
= help: should this be `@if`?
error: found keyword `else`
--> tests/warnings/keyword-without-at.rs:6:9
|
6 | else {}
| ^^^^
|
= help: should this be `@else`?
error: found keyword `for`
--> tests/warnings/keyword-without-at.rs:7:9
|
7 | for {}
| ^^^
|
= help: should this be `@for`?
error: found keyword `while`
--> tests/warnings/keyword-without-at.rs:8:9
|
8 | while {}
| ^^^^^
|
= help: should this be `@while`?
error: found keyword `match`
--> tests/warnings/keyword-without-at.rs:9:9
|
9 | match {}
| ^^^^^
|
= help: should this be `@match`?
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
ACTUAL OUTPUT:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: found keyword `if`
= help: should this be `@if`?
--> tests/warnings/keyword-without-at.rs:5:9
|
5 | if {}
| ^^
error: found keyword `else`
= help: should this be `@else`?
--> tests/warnings/keyword-without-at.rs:6:9
|
6 | else {}
| ^^^^
error: found keyword `for`
= help: should this be `@for`?
--> tests/warnings/keyword-without-at.rs:7:9
|
7 | for {}
| ^^^
error: found keyword `while`
= help: should this be `@while`?
--> tests/warnings/keyword-without-at.rs:8:9
|
8 | while {}
| ^^^^^
error: found keyword `match`
= help: should this be `@match`?
--> tests/warnings/keyword-without-at.rs:9:9
|
9 | match {}
| ^^^^^
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
note: If the actual output is the correct output you can bless it by rerunning
your test with the environment variable TRYBUILD=overwrite
test tests/warnings/let-without-block.rs ... ok
test tests/warnings/non-closed-element.rs ... ok
test tests/warnings/non-string-literal.rs ... mismatch
EXPECTED:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: literal must be double-quoted: `"42"`
--> tests/warnings/non-string-literal.rs:5:9
|
5 | 42
| ^^
error: literal must be double-quoted: `"42usize"`
--> tests/warnings/non-string-literal.rs:6:9
|
6 | 42usize
| ^^^^^^^
error: literal must be double-quoted: `"42.0"`
--> tests/warnings/non-string-literal.rs:7:9
|
7 | 42.0
| ^^^^
error: literal must be double-quoted: `"a"`
--> tests/warnings/non-string-literal.rs:8:9
|
8 | 'a'
| ^^^
error: expected string
--> tests/warnings/non-string-literal.rs:9:9
|
9 | b"a"
| ^^^^
error: expected string
--> tests/warnings/non-string-literal.rs:10:9
|
10 | b'a'
| ^^^^
error: attribute value must be a string
--> tests/warnings/non-string-literal.rs:13:15
|
13 | input disabled=true;
| ^^^^^^^^^^^^^
|
= help: to declare an empty attribute, omit the equals sign: `disabled`
= help: to toggle the attribute, use square brackets: `disabled[some_boolean_flag]`
error: attribute value must be a string
--> tests/warnings/non-string-literal.rs:14:15
|
14 | input disabled=false;
| ^^^^^^^^^^^^^^
|
= help: to declare an empty attribute, omit the equals sign: `disabled`
= help: to toggle the attribute, use square brackets: `disabled[some_boolean_flag]`
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
ACTUAL OUTPUT:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: literal must be double-quoted: `"42"`
--> tests/warnings/non-string-literal.rs:5:9
|
5 | 42
| ^^
error: literal must be double-quoted: `"42usize"`
--> tests/warnings/non-string-literal.rs:6:9
|
6 | 42usize
| ^^^^^^^
error: literal must be double-quoted: `"42.0"`
--> tests/warnings/non-string-literal.rs:7:9
|
7 | 42.0
| ^^^^
error: literal must be double-quoted: `"a"`
--> tests/warnings/non-string-literal.rs:8:9
|
8 | 'a'
| ^^^
error: expected string
--> tests/warnings/non-string-literal.rs:9:9
|
9 | b"a"
| ^^^^
error: expected string
--> tests/warnings/non-string-literal.rs:10:9
|
10 | b'a'
| ^^^^
error: attribute value must be a string
= help: to declare an empty attribute, omit the equals sign: `disabled`
= help: to toggle the attribute, use square brackets: `disabled[some_boolean_flag]`
--> tests/warnings/non-string-literal.rs:13:15
|
13 | input disabled=true;
| ^^^^^^^^^^^^^
error: attribute value must be a string
= help: to declare an empty attribute, omit the equals sign: `disabled`
= help: to toggle the attribute, use square brackets: `disabled[some_boolean_flag]`
--> tests/warnings/non-string-literal.rs:14:15
|
14 | input disabled=false;
| ^^^^^^^^^^^^^^
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
note: If the actual output is the correct output you can bless it by rerunning
your test with the environment variable TRYBUILD=overwrite
test tests/warnings/void-element-slash.rs ... mismatch
EXPECTED:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: void elements must use `;`, not `/`
--> $DIR/void-element-slash.rs:5:12
|
5 | br /
| ^
|
= help: change this to `;`
= help: see https://github.com/lambda-fairy/maud/pull/315 for details
error: void elements must use `;`, not `/`
--> $DIR/void-element-slash.rs:7:27
|
7 | input type="text" /
| ^
|
= help: change this to `;`
= help: see https://github.com/lambda-fairy/maud/pull/315 for details
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
ACTUAL OUTPUT:
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error: void elements must use `;`, not `/`
= help: change this to `;`
= help: see https://github.com/lambda-fairy/maud/pull/315 for details
--> tests/warnings/void-element-slash.rs:5:12
|
5 | br /
| ^
error: void elements must use `;`, not `/`
= help: change this to `;`
= help: see https://github.com/lambda-fairy/maud/pull/315 for details
--> tests/warnings/void-element-slash.rs:7:27
|
7 | input type="text" /
| ^
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
note: If the actual output is the correct output you can bless it by rerunning
your test with the environment variable TRYBUILD=overwrite
test run_warnings ... FAILED
failures:
---- run_warnings stdout ----
thread 'run_warnings' (1370) panicked at /usr/share/cargo/registry/trybuild-1.0.116/src/run.rs:102:13:
3 of 9 tests failed
stack backtrace:
0: __rustc::rust_begin_unwind
at /usr/src/rustc-1.94.1/library/std/src/panicking.rs:689:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.94.1/library/core/src/panicking.rs:80:14
2: <trybuild::Runner>::run
at /usr/share/cargo/registry/trybuild-1.0.116/src/run.rs:102:13
3: <trybuild::TestCases as core::ops::drop::Drop>::drop
at /usr/share/cargo/registry/trybuild-1.0.116/src/lib.rs:342:38
4: core::ptr::drop_in_place::<trybuild::TestCases>
at /usr/src/rustc-1.94.1/library/core/src/ptr/mod.rs:805:1
5: errors::run_warnings
at ./tests/errors.rs:7:1
6: errors::run_warnings::{closure#0}
at ./tests/errors.rs:4:18
7: <errors::run_warnings::{closure#0} as core::ops::function::FnOnce<()>>::call_once
at /usr/src/rustc-1.94.1/library/core/src/ops/function.rs:250:5
8: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.94.1/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
failures:
run_warnings
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 8.93s
hello! I'm trying to package the maud 0.27.0 crate into Debian, I noticed the following tests though - I'm not sure why this breaks, and it might be due to the versions of the other crates we have in Debian, but I was wondering if you have any hints/suggestions since you're more familiar with the codebase? :) Thank you!