Audit `//@ run-pass` directives in UI tests
Open
@Embers-of-the-Fire is already working on this.
Since Mar 22, 2026.
A-testsuite
C-cleanup
C-enhancement
E-tedious
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Many older UI tests still use the //@ run-pass directive, even though they could just use //@ build-pass or //@ check-pass. We should make sure that //@ run-pass is only used when needed. (For example, a test about macro expansions might be fine with just //@ check-pass, a codegen test might need //@ build-pass and a test with runtime assert_eq!s should stay on //@ run-pass.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.