From fce9638b2e60afce872b3056c19a729b1b3708be Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Fri, 10 Aug 2018 10:01:08 +0100 Subject: 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 Cc: Tomi Sarvela Acked-by: Petri Latvala --- tests/intel-ci/blacklist.txt | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'tests/intel-ci') 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.* -- cgit v1.2.3