Commit fce9638b authored by Chris Wilson's avatar Chris Wilson

intel-ci: Skip module reloads

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=106539Signed-off-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
Acked-by: Petri Latvala's avatarPetri Latvala <petri.latvala@intel.com>
parent 2b63151b
......@@ -5,6 +5,15 @@ igt@meta_test(@.*)?
igt@drv_selftest(@.*)?
igt@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@drv_module_reload(@.*)?
###############################################
# GEM
###############################################
igt@gem_busy@(?!.*basic).*hang.*
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment