Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: 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: Thu, 23 Mar 2023 08:55:42 +0100	[thread overview]
Message-ID: <20230323085542.42887c3d@maurocar-mobl2> (raw)
In-Reply-To: <20230323084933.127664f7@maurocar-mobl2>

On Thu, 23 Mar 2023 08:50:25 +0100
Mauro Carvalho Chehab <mauro.chehab@linux.intel.com> wrote:

> On Wed, 22 Mar 2023 18:44:46 +0100
> Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
> 
> > 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 ?
> 
> I did that. Then, I created a link:
> 	ln -s blacklist.txt tests/intel-ci/i915-blacklist.txt 
> 
> The rationale is to avoid breaking any existing CI pipelines that would
> be expecting to find the i915 blacklist as "blacklist.txt.".
> 
> > But that aside, imho better solution would be to just
> > add xe_* to blacklist. 
> 
> That is what I did: once renamed: I added "igt@xe_.*" to the blacklist
> file.
> 
> Unfortunately, git diff output is weird when there is a rename and
> a symlink to the same name at the same patch. If you prefer, I can
> split it on two patches to make easier to view the differences.
> 
> > I am also not sure you can include
> > one blacklist into another.
> 
> There's no such thing. Both blacklist files are independent. You
> probably got tricked by the weird output git produced with the rename
> + symlink at the same patch.

Btw, if I remove the symlink, the diff becomes nice and clean:

[PATCH] intel-ci: update blacklists to work with the Xe driver
    
It doesn't make sense to run i915 tests with Xe driver and
vice-versa. Update testlists to make it clear.
    
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/i915-blacklist.txt
similarity index 97%
rename from tests/intel-ci/blacklist.txt
rename to tests/intel-ci/i915-blacklist.txt
index 6e5cc43667cf..389a2acb7f44 100644
--- a/tests/intel-ci/blacklist.txt
+++ b/tests/intel-ci/i915-blacklist.txt
@@ -84,6 +84,10 @@ igt@kms_chamelium_frames@hdmi-.*-planes-random
 igt@vc4_.*
 igt@v3d_.*
 ###############################################
+# Intel Xe
+###############################################
+igt@xe/.*
+###############################################
 # AMD
 ###############################################
 igt@amdgpu/.*
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/.*
+###############################################
+# AMD
+###############################################
+igt@amdgpu/.*
+###############################################
+# Panfrost
+###############################################
+igt@panfrost_.*
+###############################################
+# Qualcomm
+###############################################
+igt@msm_.*

  reply	other threads:[~2023-03-23  7:55 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
2023-03-23  7:50     ` Mauro Carvalho Chehab
2023-03-23  7:55       ` Mauro Carvalho Chehab [this message]
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=20230323085542.42887c3d@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox