Skip to content

Rename incremental cfail/cpass revisions to bfail/bpass#155474

Open
Zalathar wants to merge 2 commits intorust-lang:mainfrom
Zalathar:bpass
Open

Rename incremental cfail/cpass revisions to bfail/bpass#155474
Zalathar wants to merge 2 commits intorust-lang:mainfrom
Zalathar:bpass

Conversation

@Zalathar
Copy link
Copy Markdown
Member

Long ago, UI tests were divided into compile and run tests. Later, the compile tests were further subdivided into check and build tests, to speed up tests that don't need a full build.

The same split was never applied to incremental test revisions, so the only way to perform a check build in incremental tests is (confusingly) to use a cfail revision and then specify //@ check-fail or //@ check-pass.

This PR makes room for dedicated check-fail and check-pass revisions by renaming the existing cfail and cpass revisions to bfail and bpass, since they currently perform a full build.


The test updates were done with a regex whole-word find-and-replace for c(fail|pass)(\d*), and I also took the opportunity to manually add a space after revisions: on affected lines.

r? jieyouxu

@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Apr 18, 2026

The rustc-dev-guide subtree was changed. If this PR only touches the dev guide consider submitting a PR directly to rust-lang/rustc-dev-guide otherwise thank you for updating the dev guide with your changes.

cc @BoxyUwU, @tshepang

Some changes occurred in src/tools/compiletest

cc @jieyouxu

@rustbot rustbot added A-compiletest Area: The compiletest test runner A-rustc-dev-guide Area: rustc-dev-guide A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. 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. labels Apr 18, 2026
@Zalathar
Copy link
Copy Markdown
Member Author

Some of these revisions will be renamed back to cfail/cpass when I later add support for check revisions. But I think it's easier to do this migration in one big batch now, and then migrate back on a per-test basis.

Comment thread src/doc/rustc-dev-guide/src/tests/compiletest.md
@rust-log-analyzer

This comment has been minimized.

Long ago, UI tests were divided into "compile" and "run" tests. Later, the
compile tests were further subdivided into "check" and "build" tests, to speed
up tests that don't need a full build.

The same split was never applied to incremental test revisions, so the only way
to perform a check build in incremental tests is (confusingly) to use a `cfail`
revision and then specify `//@ check-fail` or `//@ check-pass`.

This PR makes room for dedicated check-fail and check-pass revisions by
renaming the existing `cfail` and `cpass` revisions to `bfail` and `bpass`,
since they currently perform a full build.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-compiletest Area: The compiletest test runner A-rustc-dev-guide Area: rustc-dev-guide A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants