[Intel-gfx] [RFC i-g-t 2/2] extended.testlist: Remove some test-subtest combinations

[Chris Wilson]

Quoting Tvrtko Ursulin (2017-06-16 11:55:30)
> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
> 
> For tests with attempt to hit races and such by running for
> relatively long time, it seems that it might be possible to get
> by only testing some subtest-engine combinations as long as in
> total we still exercise all engines per test.
> 
> More precisely, I think that if we view our engines as fast
> (!rcs) and a little less fast (others), we group the race
> hitting tests in those two camps, we keep the same coverage
> by running each subtest against each engine group.
> 
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
> ---
>  tests/intel-ci/extended.testlist | 44 ----------------------------------------
>  1 file changed, 44 deletions(-)
> 
> diff --git a/tests/intel-ci/extended.testlist b/tests/intel-ci/extended.testlist
> index e0926ff09bcd..246a14f6e501 100644
> --- a/tests/intel-ci/extended.testlist
> +++ b/tests/intel-ci/extended.testlist
>  igt at gem_sync@blt
> -igt at gem_sync@bsd
> -igt at gem_sync@bsd1
> -igt at gem_sync@bsd2
> -igt at gem_sync@many-blt
>  igt at gem_sync@many-bsd
> -igt at gem_sync@many-bsd1
> -igt at gem_sync@many-bsd2
>  igt at gem_sync@many-render
> -igt at gem_sync@many-vebox
>  igt at gem_sync@render
> -igt at gem_sync@store-blt
> -igt at gem_sync@store-bsd
> -igt at gem_sync@store-bsd1
> -igt at gem_sync@store-bsd2
>  igt at gem_sync@store-render
>  igt at gem_sync@store-vebox
> -igt at gem_sync@vebox

The selection should be igt at gem_sync@*all* then any smattering of other
engines, if desired but coverage of races on individual engines should
already be good enough.
-Chris