[igt-dev] [PATCH i-g-t] intel-ci: Drop gem_ctx_switch trivial stress tests

[Chris Wilson]

We only use the most trivial of many-context switch stress tests in the
shards. With no verification of behaviour, they only serve to see if the
kernel explodes. We have many, many other context switches with varying
workloads and requirements that _do_ verify expected behaviour and
providing en masse good stress. We also have much more precise
verification of the context switch inside the kernel, making these
simple stress tests redundant.

However, a stress test is a stress test, so keep it around for developer
peace of mind. As usual, if a stress test ever produces a hit, we need
to reduce it down to a new test for CI.

By dropping them we remove over 10 minutes of runtime from the shards,
that afair have never produced a unique warning.

Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
---
 tests/intel-ci/blacklist.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
index 056ad7324..4bca1b6c5 100644
--- a/tests/intel-ci/blacklist.txt
+++ b/tests/intel-ci/blacklist.txt
@@ -25,7 +25,7 @@ igt at gem_cs_prefetch(@.*)?
 igt at gem_ctx_create@(?!.*basic).*
 igt at gem_ctx_exec@(?!.*basic).*
 igt at gem_ctx_shared@*exhaust*
-igt at gem_ctx_switch@.*(forked|interruptible).*
+igt at gem_ctx_switch(@.*)?
 igt at gem_ctx_thrash(@.*)?
 igt at gem_evict_alignment(@.*)?
 igt at gem_evict_everything(@.*)?
-- 
2.24.0