From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: Katarzyna Piecielska <katarzyna.piecielska@intel.com>
Subject: Re: [PATCH i-g-t v1 2/2] intel-ci/xe: Block more i915 tests in Xe runs
Date: Thu, 3 Apr 2025 10:37:32 +0200 [thread overview]
Message-ID: <26141634-5bf7-41a4-a9d4-3631168089e9@linux.intel.com> (raw)
In-Reply-To: <20250402161207.66601-3-kamil.konieczny@linux.intel.com>
On 4/2/2025 6:12 PM, Kamil Konieczny wrote:
> There was added new generic Intel test intel_sysfs_debugfs
> which checks sysfs and debugfs for both i915 and Xe.
> Lets block i915 ones for Xe runs.
>
> Cc: Katarzyna Piecielska <katarzyna.piecielska@intel.com>
> Cc: Peter Senna Tschudin <peter.senna@linux.intel.com>
> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Reviewed-by: Peter Senna Tschudin <peter.senna@linux.intel.com>
> ---
> tests/intel-ci/xe.blocklist.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/intel-ci/xe.blocklist.txt b/tests/intel-ci/xe.blocklist.txt
> index 80ceba9a5..d02d0f73e 100644
> --- a/tests/intel-ci/xe.blocklist.txt
> +++ b/tests/intel-ci/xe.blocklist.txt
> @@ -20,6 +20,7 @@ igt@gen.*
> igt@i915_.*
> igt@perf.*
> igt@sysfs_.*
> +igt@.*@i915.*
> ##################################################################
> # Exclude mock DRM KUnit from IGT, as those already run at build
> # time on Intel CI
prev parent reply other threads:[~2025-04-03 8:37 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 ` [PATCH i-g-t v1 1/2] intel-ci/i915: Block more Xe tests in i915 runs Kamil Konieczny
2025-04-02 18:27 ` 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 [this message]
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=26141634-5bf7-41a4-a9d4-3631168089e9@linux.intel.com \
--to=peter.senna@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=katarzyna.piecielska@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