Negative UI test error annotations #129460
Labels
A-compiletest
Area: The compiletest test runner
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
E-medium
Call for participation: Medium difficulty. Experience needed to fix: Intermediate.
E-needs-design
This issue needs exploration and design to see how and if we can fix/implement it
E-needs-investigation
Call for partcipation: This issues needs some investigation to determine current status
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
I wish there is a negative assertion, saying that here one shall not expect a
HELP
note.Originally posted by @dingxiangfei2009 in #107251 (comment)
Something that might be nice-to-have is negative ui test error annotations, i.e. that we explicitly want to make sure some diagnostic is not emitted (analogous to FileCheck
check-NOT
annotations).Obviously, you can rely on checking the blessed stderr, but a negative ui test annotation could help communicate intent in the test itself and is less prone to accidentally letting the blessed stderr though.
Note: we should probably try to make the directive parser more robust and less hacky before attempting to add more syntax.
The text was updated successfully, but these errors were encountered: