From 95f6fc3cb374d24d9b9c654148ccc0502f879c96 Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Fri, 14 Jul 2023 10:46:18 +0200 Subject: [PATCH] date-check: test suites/classes using "revisions" Note stolen from https://github.com/rust-lang/rust/blob/fe03b46ee4688a99d7155b4f9dcd875b6903952d/src/tools/compiletest/src/lib.rs#L727 --- src/tests/compiletest.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/src/tests/compiletest.md b/src/tests/compiletest.md index f73d2435a..f9a2dfd73 100644 --- a/src/tests/compiletest.md +++ b/src/tests/compiletest.md @@ -467,9 +467,6 @@ fn main() { ## Revisions -Certain classes of tests support "revisions" (as of 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. + +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