All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v3 1/3] intel-ci: update blacklists to work with the Xe driver
Date: Wed, 22 Mar 2023 18:44:46 +0100	[thread overview]
Message-ID: <20230322174446.75ie3nrckvetww3i@kamilkon-desk1> (raw)
In-Reply-To: <20230322140030.1800192-2-mauro.chehab@linux.intel.com>

Hi Mauro,

On 2023-03-22 at 15:00:28 +0100, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab <mchehab@kernel.org>
> 
> It doesn't make sense to run i915 tests with Xe driver and
> vice-versa. Update testlists to make it clear.
> 
> In order to avoid disrupts at exiting intel-ci tests, keep a
> symlink:
> 	i915-blacklist.txt -> blacklist.txt
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>  tests/intel-ci/blacklist.txt      | 130 +----------------------------
>  tests/intel-ci/i915-blacklist.txt | 133 ++++++++++++++++++++++++++++++

Why not just git mv oldfile newfile ?
But that aside, imho better solution would be to just
add xe_* to blacklist. I am also not sure you can include
one blacklist into another.

+Cc: Petri Latvala <adrinael@adrinael.net>

>  tests/intel-ci/xe-blacklist.txt   |  21 +++++
>  3 files changed, 155 insertions(+), 129 deletions(-)
>  mode change 100644 => 120000 tests/intel-ci/blacklist.txt
>  create mode 100644 tests/intel-ci/i915-blacklist.txt
>  create mode 100644 tests/intel-ci/xe-blacklist.txt
> 
> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
> deleted file mode 100644
> index 6e5cc43667cf..000000000000
> --- a/tests/intel-ci/blacklist.txt
> +++ /dev/null
> @@ -1,129 +0,0 @@
> -igt@meta_test(@.*)?
> -###############################################
> -# 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@i915_module_load(@.*)? # danger, danger; hope for taints!
> -igt@i915_pm_rpm@module-reload
> -igt@i915_pm_rpm@gem-execbuf-stress-extra-wait
> -###############################################
> -# GEM
> -###############################################
> -igt@gem_busy@hang.*
> -igt@gem_close_race@(?!.*basic).*
> -igt@gem_concurrent_blit(@.*)?
> -igt@gem_ctx_create@(?!.*basic).*
> -igt@gem_ctx_exec@(?!.*basic).*
> -igt@gem_ctx_shared@*exhaust*
> -igt@gem_ctx_switch(@.*)?
> -igt@gem_evict_alignment(@.*)?
> -igt@gem_evict_everything(@.*)?
> -igt@gem_exec_big@(?!.*single).*
> -igt@gem_exec_capture@many-(?!4K-).*
> -igt@gem_exec_fair@(?!.*basic).*
> -igt@gem_exec_fence@.*hang.*
> -igt@gem_exec_flush@(?!.*basic).*
> -igt@gem_exec_latency(@.*)?
> -igt@gem_exec_lut_handle(@.*)?
> -igt@gem_exec_nop@(?!.*basic).*
> -igt@gem_exec_reloc@(?!.*basic).*
> -igt@gem_exec_suspend@(?!.*basic).*
> -igt@gem_exec_whisper@(?!basic).*
> -igt@gem_fd_exhaustion(@.*)?
> -igt@gem_fence_upload(@.*)?
> -igt@gem_gtt_hog(@.*)?
> -igt@gem_gtt_speed(@.*)?
> -igt@gem_lut_handle(@.*)?
> -igt@gem_mmap_gtt@.*(huge|swap|clflush|forked).*
> -igt@gem_mmap@.*(swap|huge).*
> -igt@gem_pread_after_blit(@.*)?
> -igt@gem_pwrite@(?!.*basic).*
> -igt@gem_read_read_speed(@.*)?
> -igt@gem_render_linear_blits@(?!.*basic).*
> -igt@gem_render_tiled_blits@(?!.*basic).*
> -igt@gem_reset_stats(@.*)?
> -igt@gem_ringfill@(?!.*basic).*
> -igt@gem_shrink@(?!reclaim$).*
> -igt@gem_softpin@.*(hang|S4).*
> -igt@gem_streaming_writes(@.*)?
> -igt@gem_sync@(?!.*basic).*
> -igt@gem_tiled_swapping@(?!non-threaded).*
> -igt@gem_userptr_blits@(major|minor|forked|mlocked|swapping).*
> -igt@gem_wait@hang.*
> -igt@gem_watchdog@far-fence
> -igt@sysfs_heartbeat_interval@(long|off)
> -igt@sysfs_preempt_timeout@off
> -igt@sysfs_timeslice_duration@off
> -###############################################
> -# GEM: Not worth fixing
> -###############################################
> -igt@gen7_exec_parse@.*lri.*
> -igt@gem_exec_alignment@pi-shared
> -###############################################
> -# There are no DRRS capable displays in CI lab
> -###############################################
> -igt@kms_frontbuffer_tracking@.*drrs.*
> -###############################################
> -# Tends to generate invalid configurations
> -# using CCS planes or configurations that
> -# exceed HW capabilities resulting in sporadic
> -# failure with -EINVAL.
> -#
> -# Maintaining extra constraints for Intel's HW
> -# is too costly in comparison to the value
> -# provided.
> -###############################################
> -igt@kms_chamelium_frames@hdmi-.*-planes-random
> -###############################################
> -# Broadcom
> -###############################################
> -igt@vc4_.*
> -igt@v3d_.*
> -###############################################
> -# AMD
> -###############################################
> -igt@amdgpu/.*
> -###############################################
> -# Panfrost
> -###############################################
> -igt@panfrost_.*
> -###############################################
> -# Qualcomm
> -###############################################
> -igt@msm_.*
> -###############################################
> -# Hibernate: not configured correctly on CI
> -###############################################
> -igt@.*@.*-hibernate
> -igt@gem_softpin@noreloc-s4
> -igt@gem_workarounds@hibernate-.*
> -igt@gem_exec_suspend@basic-s4$
> -igt@gem_ctx_isolation@.*-s4
> -###############################################
> -# Out-of-memory: spammy and often broken
> -###############################################
> -igt@i915_suspend@shrink
> -###############################################
> -# pipe-e, pipe-f no current HW support
> -###############################################
> -igt@.*@.*pipe-e($|-.*)
> -igt@.*@.*pipe-f($|-.*)
> -
> -###############################################
> -# Temporary workarounds for CI-impacting bugs
> -###############################################
> -
> -# Currently fails and leaves the machine in a very bad state, and
> -# causes coverage loss for other tests. IOMMU related.
> -# https://gitlab.freedesktop.org/drm/intel/-/issues/2644
> -igt@core_hotunplug@.*(hot|plug).*
> -
> -# hangs several gens of hosts, and has no immediate fix
> -igt@device_reset@reset-bound
> -
> -# not working for i915
> -igt@kms_bw@.*
> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
> new file mode 120000
> index 000000000000..e48e29e27f4e
> --- /dev/null
> +++ b/tests/intel-ci/blacklist.txt
> @@ -0,0 +1 @@
> +i915-blacklist.txt
> \ No newline at end of file

I am not sure it will work.

> diff --git a/tests/intel-ci/i915-blacklist.txt b/tests/intel-ci/i915-blacklist.txt
> new file mode 100644
> index 000000000000..389a2acb7f44
> --- /dev/null
> +++ b/tests/intel-ci/i915-blacklist.txt
> @@ -0,0 +1,133 @@
> +igt@meta_test(@.*)?
> +###############################################
> +# 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@i915_module_load(@.*)? # danger, danger; hope for taints!
> +igt@i915_pm_rpm@module-reload
> +igt@i915_pm_rpm@gem-execbuf-stress-extra-wait
> +###############################################
> +# GEM
> +###############################################
> +igt@gem_busy@hang.*
> +igt@gem_close_race@(?!.*basic).*
> +igt@gem_concurrent_blit(@.*)?
> +igt@gem_ctx_create@(?!.*basic).*
> +igt@gem_ctx_exec@(?!.*basic).*
> +igt@gem_ctx_shared@*exhaust*
> +igt@gem_ctx_switch(@.*)?
> +igt@gem_evict_alignment(@.*)?
> +igt@gem_evict_everything(@.*)?
> +igt@gem_exec_big@(?!.*single).*
> +igt@gem_exec_capture@many-(?!4K-).*
> +igt@gem_exec_fair@(?!.*basic).*
> +igt@gem_exec_fence@.*hang.*
> +igt@gem_exec_flush@(?!.*basic).*
> +igt@gem_exec_latency(@.*)?
> +igt@gem_exec_lut_handle(@.*)?
> +igt@gem_exec_nop@(?!.*basic).*
> +igt@gem_exec_reloc@(?!.*basic).*
> +igt@gem_exec_suspend@(?!.*basic).*
> +igt@gem_exec_whisper@(?!basic).*
> +igt@gem_fd_exhaustion(@.*)?
> +igt@gem_fence_upload(@.*)?
> +igt@gem_gtt_hog(@.*)?
> +igt@gem_gtt_speed(@.*)?
> +igt@gem_lut_handle(@.*)?
> +igt@gem_mmap_gtt@.*(huge|swap|clflush|forked).*
> +igt@gem_mmap@.*(swap|huge).*
> +igt@gem_pread_after_blit(@.*)?
> +igt@gem_pwrite@(?!.*basic).*
> +igt@gem_read_read_speed(@.*)?
> +igt@gem_render_linear_blits@(?!.*basic).*
> +igt@gem_render_tiled_blits@(?!.*basic).*
> +igt@gem_reset_stats(@.*)?
> +igt@gem_ringfill@(?!.*basic).*
> +igt@gem_shrink@(?!reclaim$).*
> +igt@gem_softpin@.*(hang|S4).*
> +igt@gem_streaming_writes(@.*)?
> +igt@gem_sync@(?!.*basic).*
> +igt@gem_tiled_swapping@(?!non-threaded).*
> +igt@gem_userptr_blits@(major|minor|forked|mlocked|swapping).*
> +igt@gem_wait@hang.*
> +igt@gem_watchdog@far-fence
> +igt@sysfs_heartbeat_interval@(long|off)
> +igt@sysfs_preempt_timeout@off
> +igt@sysfs_timeslice_duration@off
> +###############################################
> +# GEM: Not worth fixing
> +###############################################
> +igt@gen7_exec_parse@.*lri.*
> +igt@gem_exec_alignment@pi-shared
> +###############################################
> +# There are no DRRS capable displays in CI lab
> +###############################################
> +igt@kms_frontbuffer_tracking@.*drrs.*
> +###############################################
> +# Tends to generate invalid configurations
> +# using CCS planes or configurations that
> +# exceed HW capabilities resulting in sporadic
> +# failure with -EINVAL.
> +#
> +# Maintaining extra constraints for Intel's HW
> +# is too costly in comparison to the value
> +# provided.
> +###############################################
> +igt@kms_chamelium_frames@hdmi-.*-planes-random
> +###############################################
> +# Broadcom
> +###############################################
> +igt@vc4_.*
> +igt@v3d_.*
> +###############################################
> +# Intel Xe
> +###############################################
> +igt@xe/.*
-------- ^
imho this should be

igt@xe_.*

> +###############################################
> +# AMD
> +###############################################
> +igt@amdgpu/.*
> +###############################################
> +# Panfrost
> +###############################################
> +igt@panfrost_.*
> +###############################################
> +# Qualcomm
> +###############################################
> +igt@msm_.*
> +###############################################
> +# Hibernate: not configured correctly on CI
> +###############################################
> +igt@.*@.*-hibernate
> +igt@gem_softpin@noreloc-s4
> +igt@gem_workarounds@hibernate-.*
> +igt@gem_exec_suspend@basic-s4$
> +igt@gem_ctx_isolation@.*-s4
> +###############################################
> +# Out-of-memory: spammy and often broken
> +###############################################
> +igt@i915_suspend@shrink
> +###############################################
> +# pipe-e, pipe-f no current HW support
> +###############################################
> +igt@.*@.*pipe-e($|-.*)
> +igt@.*@.*pipe-f($|-.*)
> +
> +###############################################
> +# Temporary workarounds for CI-impacting bugs
> +###############################################
> +
> +# Currently fails and leaves the machine in a very bad state, and
> +# causes coverage loss for other tests. IOMMU related.
> +# https://gitlab.freedesktop.org/drm/intel/-/issues/2644
> +igt@core_hotunplug@.*(hot|plug).*
> +
> +# hangs several gens of hosts, and has no immediate fix
> +igt@device_reset@reset-bound
> +
> +# not working for i915
> +igt@kms_bw@.*
> diff --git a/tests/intel-ci/xe-blacklist.txt b/tests/intel-ci/xe-blacklist.txt
> new file mode 100644
> index 000000000000..986e91a67069
> --- /dev/null
> +++ b/tests/intel-ci/xe-blacklist.txt
> @@ -0,0 +1,21 @@
> +###############################################
> +# Broadcom
> +###############################################
> +igt@vc4_.*
> +igt@v3d_.*
> +###############################################
> +# Intel i915
> +###############################################
> +igt@i915/.*
---------- ^

imho:
igt@i915_.*
igt@gem_.*

Regards,
Kamil

> +###############################################
> +# AMD
> +###############################################
> +igt@amdgpu/.*
> +###############################################
> +# Panfrost
> +###############################################
> +igt@panfrost_.*
> +###############################################
> +# Qualcomm
> +###############################################
> +igt@msm_.*
> -- 
> 2.39.2
> 


  reply	other threads:[~2023-03-22 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 14:00 [igt-dev] [PATCH i-g-t v3 0/3] xe/xe_module_load: add a test to load/unload Xe driver Mauro Carvalho Chehab
2023-03-22 14:00 ` [igt-dev] [PATCH i-g-t v3 1/3] intel-ci: update blacklists to work with the " Mauro Carvalho Chehab
2023-03-22 17:44   ` Kamil Konieczny [this message]
2023-03-23  7:50     ` Mauro Carvalho Chehab
2023-03-23  7:55       ` Mauro Carvalho Chehab
2023-03-22 14:00 ` [igt-dev] [PATCH i-g-t v3 2/3] lib/igt_kmod: add support for " Mauro Carvalho Chehab
2023-03-22 18:00   ` Kamil Konieczny
2023-03-22 14:00 ` [igt-dev] [PATCH i-g-t v3 3/3] xe/xe_module_load: add a test to load/unload " Mauro Carvalho Chehab
2023-03-22 18:13   ` Kamil Konieczny
2023-03-22 15:02 ` [igt-dev] ✓ Fi.CI.BAT: success for xe/xe_module_load: add a test to load/unload Xe driver (rev2) Patchwork
2023-03-22 19:25 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-03-23  8:27 ` [igt-dev] ✗ Fi.CI.BUILD: failure for xe/xe_module_load: add a test to load/unload Xe driver (rev3) Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230322174446.75ie3nrckvetww3i@kamilkon-desk1 \
    --to=kamil.konieczny@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.