date-check: test suites/classes using "revisions" (#1738)
This commit is contained in:
parent
991f770374
commit
ab4a6e1350
|
|
@ -467,9 +467,6 @@ fn main() {
|
|||
|
||||
## Revisions
|
||||
|
||||
Certain classes of tests support "revisions" (as of <!-- date-check --> July 2022,
|
||||
this includes UI, assembly, codegen, debuginfo, incremental, and rustdoc UI tests,
|
||||
though incremental tests are somewhat different).
|
||||
Revisions allow a single test file to be used for multiple tests.
|
||||
This is done by adding a special header at the top of the file:
|
||||
|
||||
|
|
@ -503,6 +500,15 @@ currently only apply to the test as a whole, not to particular
|
|||
revisions. The only headers that are intended to really work when
|
||||
customized to a revision are error patterns and compiler flags.
|
||||
|
||||
<!-- date-check jul 2023 -->
|
||||
Following is classes of tests that support revisions:
|
||||
- UI
|
||||
- assembly
|
||||
- codegen
|
||||
- debuginfo
|
||||
- rustdoc UI tests
|
||||
- incremental (these are special in that they inherently cannot be run in parallel)
|
||||
|
||||
## Compare modes
|
||||
|
||||
Compiletest can be run in different modes, called _compare modes_, which can
|
||||
|
|
|
|||
Loading…
Reference in New Issue