[Intel-gfx] [PATCH igt 1/2] intel-ci: Do module reload last

[Petri Latvala]

Thanks for the reminder about this ordering change.

The crash from disable_display use will cause $stuff in CI, its
ability to recover and resume is not quite there yet. But as it's at
the end, we can live with it until a fix lands.

Series is
Acked-by: Petri Latvala <petri.latvala at intel.com>


On Wed, Jan 18, 2017 at 09:58:12AM +0000, Chris Wilson wrote:
> We want to run the initial set of tests under "pristine startup"
> conditions - so that our tests see the hardware as close to the
> condition we normally would after booting. This means that we want to
> avoid reloading the module until the very last set of tests.
> 
> 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 42042f18..a6b56f35 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -3,9 +3,6 @@ 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
> @@ -244,3 +241,6 @@ 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
> +igt at drv_module_reload@basic-reload-inject
> +igt at drv_module_reload@basic-reload-final
> -- 
> 2.11.0
>