rust/tests/rustdoc-ui/issues/issue-81662-shortness.rs

//@ compile-flags:--test --error-format=short
//@ check-stdout
//@ error-pattern:cannot find function `foo`
//@ normalize-stdout-test: "tests/rustdoc-ui/issues" -> "$$DIR"
//@ normalize-stdout-test: "finished in \d+\.\d+s" -> "finished in $$TIME"
//@ failure-status: 101

/// ```rust
/// foo();
/// ```
fn foo() {
    println!("Hello, world!");
}
Add a test for the shortness format in rustdoc 2021-02-04 11:59:42 -06:00			`//@ compile-flags:--test --error-format=short`
Switch from using `//~ERROR` annotations with `--error-format` to `error-pattern` Resolves Issue #118752 2023-12-21 03:44:43 -06:00			`//@ check-stdout`
On short error format, append primary span label to message The `error-format=short` output only displays the path, error code and main error message all in the same line. We now add the primary span label as well after the error message, to provide more context. 2024-06-21 14:22:59 -05:00			//@ error-pattern:cannot find function `foo`
Move some rustdoc-ui tests to subdirectories 2023-04-29 04:08:33 -05:00			`//@ normalize-stdout-test: "tests/rustdoc-ui/issues" -> "$$DIR"`
Always use a colon in `//@ normalize-*:` headers 2024-06-21 00:15:36 -05:00			`//@ normalize-stdout-test: "finished in \d+\.\d+s" -> "finished in $$TIME"`
Add a test for the shortness format in rustdoc 2021-02-04 11:59:42 -06:00			`//@ failure-status: 101`

			/// ```rust
			`/// foo();`
			/// ```
			`fn foo() {`
			`println!("Hello, world!");`
			`}`