about summary refs log tree commit diff
path: root/compiler/rustc_parse
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2025-04-03 12:05:32 +0000
committerbors <bors@rust-lang.org>2025-04-03 12:05:32 +0000
commit946aea0b3d9f43e57953ce5094d8e4a2a244ce71 (patch)
tree3d8fec4dfe48f821804107325d4bbe571f5f5bf3 /compiler/rustc_parse
parente0883a2a6c8e4afcb6e26a182885f687ba63a7f5 (diff)
parent4916d44b59a2b5347506b4551b389fe902bdf54b (diff)
downloadrust-946aea0b3d9f43e57953ce5094d8e4a2a244ce71.tar.gz
rust-946aea0b3d9f43e57953ce5094d8e4a2a244ce71.zip
Auto merge of #139137 - petrochenkov:errwhere2, r=jieyouxu
compiletest: Require `//~` annotations even if `error-pattern` is specified

This is continuation of #138865 with some help from #139100.

`error-pattern` annotations that duplicate the newly added `//~` annotations are removed, other `error-pattern`s are not touched yet.

In exceptional cases `//@ compile-flags: --error-format=human` can be used to opt out of these checks.
In this PR I only had to use the opt out 3 times:
- `tests/ui/parser/utf16-{be,le}-without-bom.rs` - there are too many errors that are nearly identical (modulo location), because an error is reported on every second symbol
- `tests/ui-fulldeps/missing-rustc-driver-error.rs` - the errors list various rustc crate dependencies and may unexpectedly invalidate on random rustc changes
Diffstat (limited to 'compiler/rustc_parse')
0 files changed, 0 insertions, 0 deletions