-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compiletest is misled by comments talking about src/test/run-pass/ dir #49860
Comments
// run-pass
check is fooled by // stuff talking about run-pass/ dir
Seems slightly odd, because the tests for rust/src/tools/compiletest/src/header.rs Lines 523 to 525 in 0b72d48
rust/src/tools/compiletest/src/header.rs Lines 602 to 609 in 0b72d48
And the check for the start of the line: rust/src/tools/compiletest/src/header.rs Lines 439 to 441 in 0b72d48
|
Its possible that I misdiagnosed the reason that issue-23338-locals-die-before-temps-of-body.rs "worked" without adding I'll try to dobule check. |
Ah, I see: I think I misinterpreted what's happening in issue-23338-locals-die-before-temps-of-body.rs Namely, the test isn't succeeding. The compiler is ICE'ing! |
Discovered while working on #48879
Due to #49855 I am forcing a number of tests without a
// run-pass
directive to explicitly always fall in any compilation mode.I was surprised to discover one of the tests was emitting no errors but it wasn't one of the ones I had to force a failure on, and yet it was not tagged as
// run-pass
.This was this test: https://github.com/rust-lang/rust/blob/master/src/test/ui/span/issue-23338-locals-die-before-temps-of-body.rs
The problem is that this occurs on line 14 of the test:
which AFAICT is probably matching some regexp in
compiletest
e.g. like^//.*run-pass.*$
The text was updated successfully, but these errors were encountered: