Debian Codegraph @

tests/intel-ci/README

raw
1 This directory contains test lists that are used by Intel's CI. The
2 files are passed to piglit with the --test-list parameter directly.
3
4 The test lists are contained in the IGT repository for several
5 reasons:
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
16 Changing the test lists should only happen with approval from the CI
17 people. If you make a new test that should be tested by CI regularly,
18 ask a maintainer (see MAINTAINERS).
19
20 ===========================
21 i915.fast-feedback.testlist
22 ===========================
23
24 Fast-feedback contains tests that roughly tests a wide coverage of
25 features in a short time. If the tests in fast-feedback report no
26 regressions, the (almost) full suite of IGT tests is executed for
27 proper testing. Results of a fast-feedback test round should only be
28 considered to mean that the kernel is not obviously broken.
29
30 The results of CI runs on drm-tip and various other kernel trees can
31 be found in https://intel-gfx-ci.01.org/CI/
32
33 ==================
34 i915.blocklist.txt
35 ==================
36
37 This file contains regular expressions (one per line) for tests that
38 are not to be executed in full suite test rounds.
39
40 ============================
41 i915.blocklist-pre-merge.txt
42 ============================
43
44 This file contains regular expressions (one per line) for tests that
45 are not to be executed in pre-merge full suite test rounds.
46
47 =============
48 meta.testlist
49 =============
50
51 Meta-testlist contains tests that are hardcoded to generate various
52 different test results. It is used to test CI systems for proper
53 result reporting, notification systems, etc.