Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	Peter Senna Tschudin <peter.senna@linux.intel.com>
Subject: [PATCH i-g-t v1 1/2] intel-ci/i915: Block more Xe tests in i915 runs
Date: Wed,  2 Apr 2025 18:12:05 +0200	[thread overview]
Message-ID: <20250402161207.66601-2-kamil.konieczny@linux.intel.com> (raw)
In-Reply-To: <20250402161207.66601-1-kamil.konieczny@linux.intel.com>

There was recently added new generic Intel test
intel_sysfs_debugfs@xe-debugfs-read-all-entries which is causing
a valid skip on DG2. Lets block all similar Xe tests from i915
runs.

Cc: Peter Senna Tschudin <peter.senna@linux.intel.com>
Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13983
Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.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 9917bf46a..1afea1c86 100644
--- a/tests/intel-ci/blacklist.txt
+++ b/tests/intel-ci/blacklist.txt
@@ -2,6 +2,7 @@
 # This file is for non-Xe tests only
 ###############################################
 igt@xe.*
+igt@.*@xe.*
 
 igt@meta_test(@.*)?
 
-- 
2.49.0


  reply	other threads:[~2025-04-02 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02 16:12 [PATCH i-g-t v1 0/2] Block i915/Xe on Xe/i915 runs Kamil Konieczny
2025-04-02 16:12 ` Kamil Konieczny [this message]
2025-04-02 18:27   ` [PATCH i-g-t v1 1/2] intel-ci/i915: Block more Xe tests in i915 runs Mishra, Pallavi
2025-04-03  8:37   ` Peter Senna Tschudin
2025-04-02 16:12 ` [PATCH i-g-t v1 2/2] intel-ci/xe: Block more i915 tests in Xe runs Kamil Konieczny
2025-04-02 18:28   ` Mishra, Pallavi
2025-04-03  8:37   ` Peter Senna Tschudin

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=20250402161207.66601-2-kamil.konieczny@linux.intel.com \
    --to=kamil.konieczny@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=peter.senna@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