compiletest: path normalizations are sensitive to diagnostics width, can lead to confusing failures #135288
Labels
A-compiletest
Area: The compiletest test runner
A-compiletest-normalizations
Area: compiletest normalizations
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
D-diagnostic-infra
Diagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
See discussions at https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/.60tests.5Cui.5Ctraits.5Cfn-pointer.5Cbare-fn-no-impl-fn-ptr-99875.2Ers.60 about tests like
tests/ui/traits/fn-pointer/bare-fn-no-impl-fn-ptr-99875.rs
.Example:
Before compiletest path normalization, the length of the parent directories leading to the test file e.g.
F:\rust\
vsF:\Longer\rust\
can influence the specific diagnostics shown as it affects the width.The text was updated successfully, but these errors were encountered: