The test tests/ui/consts/const-eval/parse_ints.rs in the file failing-ui-tests.txt even though this is not something to fix on our end.
The reason it is not removed is because the test file doesn't contain any error pattern like //@ error-pattern: and we only remove tests containing those patterns.
According to the documentation, a UI test is expected to generate a compile error by default, so perhaps we should only keep the tests with one of the pass headers:
//@ check-pass
//@ build-pass
//@ run-pass
The test
tests/ui/consts/const-eval/parse_ints.rsin the filefailing-ui-tests.txteven though this is not something to fix on our end.The reason it is not removed is because the test file doesn't contain any error pattern like
//@ error-pattern:and we only remove tests containing those patterns.According to the documentation, a UI test is expected to generate a compile error by default, so perhaps we should only keep the tests with one of the pass headers:
//@ check-pass//@ build-pass//@ run-pass