[Intel-gfx] [PATCH i-g-t 2/2] intel-ci: Skip module reloads

[Chris Wilson]

Reloading the module may impact subsequent tests by destabilising the
system. As we do for BAT, if we want to test reloads, it should be
handled explicitly at the end of the run, rather than placed at random
in the middle of the test list.

v2: Commentary

References: https://bugs.freedesktop.org/show_bug.cgi?id=106539
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Tomi Sarvela <tomi.p.sarvela at intel.com>
---
 tests/intel-ci/blacklist.txt | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
index 7700a60b7..c93554a37 100644
--- a/tests/intel-ci/blacklist.txt
+++ b/tests/intel-ci/blacklist.txt
@@ -5,6 +5,15 @@ igt at meta_test(@.*)?
 igt at drv_selftest(@.*)?
 igt at drm_mm(@.*)?
 ###############################################
+# Handle module reloads with great care!
+#
+# Reloading a module is more likely to leave
+# the machine in an unexpected state than other
+# self-contained tests, leading to random
+# failures in tests run afterwards.
+###############################################
+igt at drv_module_reload(@.*)?
+###############################################
 # GEM
 ###############################################
 igt at gem_busy@(?!.*basic).*hang.*
-- 
2.18.0