mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
63028ac3a1
rust/tests/rustdoc-ui/check-attr.stderr

176 lines
4.0 KiB
Plaintext
Raw Normal View History

Add UI tests for new rustdoc lint
2020-04-21 17:58:52 -05:00
error: unknown attribute `compile-fail`. Did you mean `compile_fail`?
--> $DIR/check-attr.rs:3:1
|
LL | / /// foo
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
bless rustdoc-ui
2022-09-23 13:34:34 -05:00
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
Add UI tests for new rustdoc lint
2020-04-21 17:58:52 -05:00
note: the lint level is defined here
--> $DIR/check-attr.rs:1:9
|
Rename rustdoc lints to be a tool lint instead of built-in. - Rename `broken_intra_doc_links` to `rustdoc::broken_intra_doc_links` - Ensure that the old lint names still work and give deprecation errors - Register lints even when running doctests Otherwise, all `rustdoc::` lints would be ignored. - Register all existing lints as removed This unfortunately doesn't work with `register_renamed` because tool lints have not yet been registered when rustc is running. For similar reasons, `check_backwards_compat` doesn't work either. Call `register_removed` directly instead. - Fix fallout + Rustdoc lints for compiler/ + Rustdoc lints for library/ Note that this does *not* suggest `rustdoc::broken_intra_doc_links` for `rustdoc::intra_doc_link_resolution_failure`, since there was no time when the latter was valid.
2020-12-29 22:16:16 -06:00
LL | #![deny(rustdoc::invalid_codeblock_attributes)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Add UI tests for new rustdoc lint
2020-04-21 17:58:52 -05:00
error: unknown attribute `compilefail`. Did you mean `compile_fail`?
--> $DIR/check-attr.rs:3:1
|
LL | / /// foo
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
error: unknown attribute `comPile_fail`. Did you mean `compile_fail`?
--> $DIR/check-attr.rs:3:1
|
LL | / /// foo
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
error: unknown attribute `should-panic`. Did you mean `should_panic`?
--> $DIR/check-attr.rs:13:1
|
LL | / /// bar
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
error: unknown attribute `shouldpanic`. Did you mean `should_panic`?
--> $DIR/check-attr.rs:13:1
|
LL | / /// bar
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
error: unknown attribute `sHould_panic`. Did you mean `should_panic`?
--> $DIR/check-attr.rs:13:1
|
LL | / /// bar
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
error: unknown attribute `no-run`. Did you mean `no_run`?
--> $DIR/check-attr.rs:23:1
|
LL | / /// foobar
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
error: unknown attribute `norun`. Did you mean `no_run`?
--> $DIR/check-attr.rs:23:1
|
LL | / /// foobar
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
error: unknown attribute `no_Run`. Did you mean `no_run`?
--> $DIR/check-attr.rs:23:1
|
LL | / /// foobar
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
error: unknown attribute `test-harness`. Did you mean `test_harness`?
remove allow_fail test flag
2022-01-28 04:31:49 -06:00
--> $DIR/check-attr.rs:33:1
Add UI tests for new rustdoc lint
2020-04-21 17:58:52 -05:00
|
LL | / /// b
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
error: unknown attribute `testharness`. Did you mean `test_harness`?
remove allow_fail test flag
2022-01-28 04:31:49 -06:00
--> $DIR/check-attr.rs:33:1
Add UI tests for new rustdoc lint
2020-04-21 17:58:52 -05:00
|
LL | / /// b
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
error: unknown attribute `teSt_harness`. Did you mean `test_harness`?
remove allow_fail test flag
2022-01-28 04:31:49 -06:00
--> $DIR/check-attr.rs:33:1
Add UI tests for new rustdoc lint
2020-04-21 17:58:52 -05:00
|
LL | / /// b
LL | |
LL | |
LL | |
... |
LL | | /// boo
LL | | /// ```
| |_______^
|
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
remove allow_fail test flag
2022-01-28 04:31:49 -06:00
error: aborting due to 12 previous errors
Add UI tests for new rustdoc lint
2020-04-21 17:58:52 -05:00
Reference in New Issue Copy Permalink