1This directory contains test lists that are used by Intel's CI. The
2files are passed to piglit with the --test-list parameter directly.
3
4The test lists are contained in the IGT repository for several
5reasons:
6
7- The lists stay synchronized with the IGT codebase.
8- Public availability. Kernel developers can see what tests are run,
9  and can see what changes are done to the set, when, and why.
10- Explicit test lists in general make it possible to implement a new
11  test without having it run in CI (accidentally or on purpose) before
12  CI is ready for it, and for CI to stop running a test without
13  removing the test or changing its name. The previous method of test
14  selection was based on name patterns.
15
16Changing the test lists should only happen with approval from the CI
17people. If you make a new test that should be tested by CI regularly,
18ask a maintainer (see MAINTAINERS).
19
20======================
21fast-feedback.testlist
22======================
23
24Fast-feedback contains tests that roughly tests a wide coverage of
25features in a short time. If the tests in fast-feedback report no
26regressions, the (almost) full suite of IGT tests is executed for
27proper testing. Results of a fast-feedback test round should only be
28considered to mean that the kernel is not obviously broken.
29
30The results of CI runs on drm-tip and various other kernel trees can
31be found in https://intel-gfx-ci.01.org/CI/
32
33=============
34blacklist.txt
35=============
36
37This file contains regular expressions (one per line) for tests that
38are not to be executed in full suite test rounds.
39
40=============
41meta.testlist
42=============
43
44Meta-testlist contains tests that are hardcoded to generate various
45different test results. It is used to test CI systems for proper
46result reporting, notification systems, etc.
47