[Intel-gfx] [PATCH igt] intel-ci: Do module loads first + last

[Chris Wilson]

Do the module reload test first, so that it has the best chance of
succeeding without outside influence (broken driver). And then do it
last, so that it has the best chance of catching some missing
finalisation (e.g. memleak) over the lifetime of the testing.

Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Petri Latvala <petri.latvala at intel.com>
---
 tests/intel-ci/fast-feedback.testlist | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
index e25facf3..b79b0c14 100644
--- a/tests/intel-ci/fast-feedback.testlist
+++ b/tests/intel-ci/fast-feedback.testlist
@@ -1,11 +1,10 @@
+igt at drv_module_reload@basic-reload
+igt at drv_module_reload@basic-reload-inject
 igt at core_auth@basic-auth
 igt at core_prop_blob@basic
 igt at drv_getparams_basic@basic-eu-total
 igt at drv_getparams_basic@basic-subslice-total
 igt at drv_hangman@error-state-basic
-igt at drv_module_reload@basic-reload
-igt at drv_module_reload@basic-reload-inject
-igt at drv_module_reload@basic-reload-final
 igt at gem_basic@bad-close
 igt at gem_basic@create-close
 igt at gem_basic@create-fd-close
@@ -245,3 +244,4 @@ igt at vgem_basic@mmap
 igt at vgem_basic@second-client
 igt at vgem_basic@sysfs
 igt at vgem_basic@unload
+igt at drv_module_reload@basic-reload-final # keep last
-- 
2.11.0