compiletest: error-pattern and warnings are not checked in run-pass tests

[michaelwoerister]

There are some run-pass tests that seemingly check whether a specific warning or error is emitted. As far as I can tell though, the compiletest tool just ignores the given directives in a run-pass test case, i.e. changing the given directives to something unexpected still lets the tests pass.

Some affected test cases (in no particular order):

• attr-before-view-item.rs
• attr-before-view-item2.rs
• deprecated-macro_escape-inner.rs
• deprecated-macro_escape.rs
• deriving-meta-empty-trait-list.rs
• liveness-assign-imm-local-after-ret.rs
• unreachable-code-1.rs
• auxiliary/const_fn_lib.rs
• auxiliary/issue_3136_a.rs
• enum-size-variance.rs
• issue-25757.rs
• pred-not-bool.rs
• issue-19100.rs
• issue-2611-3.rs

cc @rust-lang/compiler @rust-lang/tools

[brson]

Nice catch.

[brson]

An easy way to get started fixing this is to add proper checks for the warnings to run-pass. It should be relatively easy to crib off the compile-fail code to figure out how to do it.

Additionally add code that makes error directives //~ERROR or error-pattern into errors since they don't make sense in run-pass tests.

For any tests that begin to fail because of these changes, if the fix is obvious, then fix it, otherwise check with the author of those tests (or ask here) to figure out how to proceed.

[terrynsun]

Can I try working on this?

[michaelwoerister]

@terrynsun Absolutely!

You might want to take a look at the implementation of compiletest::runtest::run_cfail_test for clues on what to add to compiletest::runtest::run_rpass_test.

[ahmedcharles]

I have a fix for this, I just need a few other PRs to land first.

[terrynsun]

Cool! Sorry for taking so long to try to work on this.

This should be closed, since the associated PR is in tree, right?

[michaelwoerister]

@Michael-Zapata True, thanks for the reminder!