[igt-dev] [i-g-t] intel-ci: balcklist gem_exec_alignment at pi-shared

Petri Latvala petri.latvala at intel.com
Wed Nov 24 11:55:31 UTC 2021


On Wed, Nov 24, 2021 at 05:02:32PM +0530, Mastan Katragadda wrote:
> black list the test until locking contentions got fixed in kernel
> 
> Signed-off-by: Mastan Katragadda <mastanx.katragadda at intel.com>
> ---
>  tests/intel-ci/blacklist.txt | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
> index ca361fde..8e9767b1 100644
> --- a/tests/intel-ci/blacklist.txt
> +++ b/tests/intel-ci/blacklist.txt
> @@ -61,6 +61,7 @@ igt at sysfs_timeslice_duration@off
>  ###############################################
>  # GEM: Not worth fixing
>  ###############################################
> +igt at gem_exec_alignment@pi-shared
>  igt at gen7_exec_parse@.*lri.*

"Not worth fixing" and "until fixed" are different messages.

This needs a bug report link, and some asssessment in the commit
message that gives rationale for not running this test while there's a
lock contention bug. A quick look at one result for that test just
says it fails, it doesn't even taint the kernel. Why does it need
blacklisting?


-- 
Petri Latvala


More information about the igt-dev mailing list