diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2018-08-10 10:01:08 +0100 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2018-08-10 11:02:06 +0100 |
commit | fce9638b2e60afce872b3056c19a729b1b3708be (patch) | |
tree | 32d292b8fbefc3a83b4026bed7721d2115b06815 | |
parent | 2b63151b004c128847e150be420b6b9eb58aafdf (diff) |
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=106539
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
-rw-r--r-- | tests/intel-ci/blacklist.txt | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt index 7700a60b..c93554a3 100644 --- a/tests/intel-ci/blacklist.txt +++ b/tests/intel-ci/blacklist.txt @@ -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.* |