rust/src/test/ui-fulldeps/lint-plugin.stderr

warning: item is named 'lintme'
  --> $DIR/lint-plugin.rs:18:1
   |
LL | fn lintme() { } //~ WARNING item is named 'lintme'
   | ^^^^^^^^^^^^^^^
   |
   = note: #[warn(test_lint)] on by default
Introduce 'run-pass' header to 'ui' tests in compiletest. Fix issue #36516. The 'run-pass' header cause a 'ui' test to execute the result. It is used to test the lint output, at the same time ensure those lints won't cause the source code to become compile-fail. 12 run-pass/run-pass-fulldeps tests gained the header and are moved to ui/ui-fulldeps. After this move, no run-pass/run-pass-fulldeps tests should rely on the compiler's JSON message. This allows us to stop passing `--error-format json` in run-pass tests, thus fixing #36516. 2017-05-13 04:54:50 -05:00			`warning: item is named 'lintme'`
			`--> $DIR/lint-plugin.rs:18:1`
			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| fn lintme() { } //~ WARNING item is named 'lintme'`
Introduce 'run-pass' header to 'ui' tests in compiletest. Fix issue #36516. The 'run-pass' header cause a 'ui' test to execute the result. It is used to test the lint output, at the same time ensure those lints won't cause the source code to become compile-fail. 12 run-pass/run-pass-fulldeps tests gained the header and are moved to ui/ui-fulldeps. After this move, no run-pass/run-pass-fulldeps tests should rely on the compiler's JSON message. This allows us to stop passing `--error-format json` in run-pass tests, thus fixing #36516. 2017-05-13 04:54:50 -05:00			`\| ^^^^^^^^^^^^^^^`
			`\|`
			`= note: #[warn(test_lint)] on by default`