All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"kamil.konieczny@linux.intel.com"
	<kamil.konieczny@linux.intel.com>,
	"Filipchuk, Julia" <julia.filipchuk@intel.com>
Subject: Re: [PATCH i-g-t v2 3/3] tests/intel-ci: Allow PXP negative testing on CRI.
Date: Thu, 10 Sep 2026 23:16:03 +0000	[thread overview]
Message-ID: <e4caa78baf45ee1cc255e3977b0a2f220fc7433f.camel@intel.com> (raw)
In-Reply-To: <20260910144309.67bggi2b2ow6rtum@kamilkon-DESK.igk.intel.com>

On Thu, 2026-09-10 at 16:43 +0200, Kamil Konieczny wrote:
> Hi Alan,
> On 2026-09-08 at 17:27:06 -0700, Alan Previn wrote:
> > igt:xe_pxp:pxp-bo-alloc/pxp-queue-alloc subtests should be run
> > on platforms that don't support PXP since they would perform
> > negative testing.
> > 
> > Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> 
> Applied with fixes in commit subjects and descriptions.
Thanks Kamil for the RB and the fixes+apply.
> 
> 
> 
> Regards,
> Kamil
> 
> > ---
> >  tests/intel-ci/xe.cri.core.blocklist.txt | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/tests/intel-ci/xe.cri.core.blocklist.txt b/tests/intel-ci/xe.cri.core.blocklist.txt
> > index 12085c4df..4172f055b 100644
> > --- a/tests/intel-ci/xe.cri.core.blocklist.txt
> > +++ b/tests/intel-ci/xe.cri.core.blocklist.txt
> > @@ -9,11 +9,11 @@ igt@fbdev@.*
> >  # Valid skip: Features / hardware blocks not present on CRI
> >  #   - xe_huc_copy@: No HuC support on CRI.
> >  #   - xe_oa@oa-tlb-invalidate: valid only for older gen12 platforms.
> > -#   - xe_pxp@.*: No PXP (Protected Xe Path) support on CRI.
> > +#   - xe_pxp@.*: No PXP on CRI so skip except negative-pxp tests
> >  ##################################################################
> >  igt@xe_huc_copy@.*
> >  igt@xe_oa@oa-tlb-invalidate
> > -igt@xe_pxp@.*
> > +igt@xe_pxp@(?!pxp-bo-alloc$|pxp-queue-alloc$).*
> >  ##################################################################
> >  # Valid skip: multigpu runs in separate config
> >  ##################################################################
> > -- 
> > 2.43.0
> > 


  reply	other threads:[~2026-09-10 23:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  0:27 [PATCH i-g-t v2 0/3] tests/intel-ci: Enable PXP coverage on PTL, CRI and BAT Alan Previn
2026-09-09  0:27 ` [PATCH i-g-t v2 1/3] tests/intel-ci: remove pxp from PTL blocklist Alan Previn
2026-09-09 16:30   ` Kamil Konieczny
2026-09-09  0:27 ` [PATCH i-g-t v2 2/3] tests/intel-ci: Add a subset of pxp tests into xe-fast-feedback Alan Previn
2026-09-09 16:31   ` Kamil Konieczny
2026-09-09  0:27 ` [PATCH i-g-t v2 3/3] tests/intel-ci: Allow PXP negative testing on CRI Alan Previn
2026-09-09 16:44   ` Kamil Konieczny
2026-09-10 14:43   ` Kamil Konieczny
2026-09-10 23:16     ` Teres Alexis, Alan Previn [this message]
2026-09-09  1:38 ` ✗ Xe.CI.BAT: failure for tests/intel-ci: Enable PXP coverage on PTL, CRI and BAT (rev2) Patchwork
2026-09-09  1:52 ` ✓ i915.CI.BAT: success " Patchwork
2026-09-09  9:25 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-09 20:06 ` ✗ i915.CI.Full: " 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=e4caa78baf45ee1cc255e3977b0a2f220fc7433f.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=julia.filipchuk@intel.com \
    --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 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.