1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
|
###############################################################################
# This test has caught regressions in the past, but the feature is rarely used
# by our users, yet it is responsible a significant portion of our execution
# time:
#
# - shard-skl: 10.2% (~22 minutes)
# - shard-kbl: 6% (~8 minutes)
# - shard-apl: 3.9% (~7 minutes)
# - shard-glk: 8% (~18 minutes)
# - shard-icl: 11% (~22 minutes)
# - shard-tgl: 7.1% (~14 minutes)
#
# Some patches already appeared to reduce the run time so this will likely not
# remain for long.
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1280
#
# Data acquired on 2020-02-19 by Martin Peres
###############################################################################
igt@kms_rotation_crc@.*
###############################################################################
# These 4 tests catching a lot of unrelated issues and are responsible for a
# significant portion of our execution time:
#
# - shard-skl: 1.6% (~4 minutes)
# - shard-kbl: 0.4% (30 seconds)
# - shard-apl: 0.2% (20 seconds)
# - shard-glk: 0.2% (30 seconds)
# - shard-icl: 6% (~12 minutes)
# - shard-tgl: 6% (~12 minutes)
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1281
#
# Data acquired on 2020-02-19 by Martin Peres
###############################################################################
igt@i915_pm_rpm@legacy-planes(-dpms)?
igt@i915_pm_rpm@universal-planes(-dpms)?
###############################################################################
# These tests are checking the obj->mm.get_page cache which is used for all
# page lookups in the driver by using a rather outdated method (pwrite) because
# it is harder to predictably exercise the cache from userspace.
#
# Until these 8 tests are replaced with a kernel selftest and removed from IGT,
# let's blacklist them for pre-merge testing as they are responsible for a
# significant portion of our execution time:
#
# - shard-skl: 0.1% (~15 seconds)
# - shard-kbl: 3.5% (~4.5 minutes)
# - shard-apl: 10% (~18 minutes)
# - shard-glk: 6.3% (~14 minutes)
# - shard-icl: 1.7% (~3.5 minutes)
# - shard-tgl: 1.6% (~3 minutes)
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1283
#
# Data acquired on 2020-02-19 by Martin Peres
###############################################################################
igt@gem_pwrite@big-.*
###############################################################################
# This test checks some edge cases of the execbuf API, which is quite time
# consuming and rarely changes. Very unlikely to be affected by any code
# outside of drm_mm and i915_gem_execbuffer, for which the authors assure us
# that they are making deliberate and well tested changes.
###############################################################################
igt@gem_exec_alignment@.*
###############################################################################
# These 4 tests are covering an edge case which should never be hit by users
# unless we already are in a bad situation, yet they are responsible for a
# significant portion of our execution time:
#
# - shard-skl: 2% (~5 minutes)
# - shard-kbl: 4% (~5 minutes)
# - shard-apl: 2.7% (~5 minutes)
# - shard-glk: 4.5% (~10 minutes)
# - shard-icl: 2.5% (~5 minutes)
# - shard-tgl: 3.5% (~7 minutes)
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1284
#
# Data acquired on 2020-02-20 by Martin Peres
###############################################################################
igt@kms_flip@flip-vs-modeset-vs-hang(-interruptible)?
igt@kms_flip@flip-vs-panning-vs-hang(-interruptible)?
###############################################################################
# These 28 tests are covering an edge case which should never be hit by users
# unless we already are in a bad situation, yet they are responsible for a
# significant portion of our execution time:
#
# - shard-skl: 1.7% (~4 minutes)
# - shard-kbl: 2.8% (~3.5 minutes)
# - shard-apl: 2.2% (~4 minutes)
# - shard-glk: 1.8% (~4 minutes)
# - shard-icl: 1.9% (~4 minutes)
# - shard-tgl: 2.8% (~5.5 minutes)
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1285
#
# Data acquired on 2020-02-20 by Martin Peres
###############################################################################
igt@kms_busy@.*hang.*
###############################################################################
# This test is reading one file at a time while being suspended, which makes
# testing extremelly slow. This is a developer-only feature which is also used
# by IGT extensively so removing it may make it harder for developers to
# understand what they regressed, but given the amount of time we can save, I
# this is an acceptable trade-off (easy-to-read report vs CI exec time):
#
# - shard-skl: 0.5% (~1 minute)
# - shard-kbl: 0.1% (~2 seconds)
# - shard-apl: 0.1% (~2 seconds)
# - shard-glk: 0.1% (~2 seconds)
# - shard-icl: 0.6% (~1.5 minutes)
# - shard-tgl: 0.7% (~1.5 minutes)
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1279
#
# Data acquired on 2020-02-20 by Martin Peres
###############################################################################
igt@i915_pm_rpm@debugfs-read
###############################################################################
# Modern userspace does not depend on the GTT anymore, so let's drop the
# slowest tests from pre-merge testing:
#
# - shard-skl: 2.7% (~6.5 minutes)
# - shard-kbl: 2% (~2.5 minutes)
# - shard-apl: 4.7% (~8.5 minutes)
# - shard-glk: 3.5% (~8 minutes)
# - shard-icl: 4.2% (~8.5 minutes)
# - shard-tgl: 2.5% (~4.5 minutes)
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1286
#
# Data acquired on 2020-02-20 by Martin Peres
###############################################################################
igt@gem_fence_thrash@bo-write-verify-threaded-[xy]
igt@gem_tiled_blits@interruptible
igt@gem_tiled_fence_blits@normal
igt@gem_tiled_blits@normal
igt@gem_tiled_wc
###############################################################################
# This is a useful test, but it mostly tests the HW rather than the driver.
# Very few regressions should be caught by this test as the driver code should
# be relatively left untouched. Hopefully, it will get optimized to be made
# useful in pre-merge as well:
#
# - shard-skl: 1% (~2.5 minutes)
# - shard-kbl: 1.5% (~2 minutes)
# - shard-apl: 1.4% (~2.5 minutes)
# - shard-glk: 2% (~4.5 minutes)
# - shard-icl: 2.7% (~5.5 minutes)
# - shard-tgl: 2.3% (~4.5 minutes)
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1287
#
# Data acquired on 2020-02-20 by Martin Peres
###############################################################################
igt@kms_plane@pixel-format-pipe-[a-d]-planes(-source-clamping)?
###############################################################################
# This test is doing nothing more than waiting for the driver to be suspended
# before issueing a modeset. However, it never failed while testing for this
# in the past year, so we probably just want to drop the amount of rounds to
# reduce the runtime, but let's just blacklist it in pre-merge for now:
#
# - shard-skl: 1% (~2.5 minute)
# - shard-kbl: 0.9% (~1 minute)
# - shard-apl: 0.6% (~1 minute)
# - shard-glk: 0.5% (~1 minute)
# - shard-icl: 1.1% (~2.5 minutes)
# - shard-tgl: 1.4% (~2.5 minutes)
#
# Issue: https://gitlab.freedesktop.org/drm/intel/issues/1288
#
# Data acquired on 2020-02-20 by Martin Peres
###############################################################################
igt@i915_pm_rpm@modeset-stress-extra-wait
|
