From 8082f48d4389c2885daecfc5b626a5f97d914dc0 Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Sun, 27 Aug 2023 02:59:53 +0200 Subject: [PATCH] date-check: test suites/classes using "revisions" (#1738) --- 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 86ebe3a49..9c969bff9 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