Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for Enable GSC loading and PXP for NVL-S
Date: Tue, 29 Sep 2026 18:24:34 +0000	[thread overview]
Message-ID: <073cb12a539b63aed0e051d3c526cfe36b757a6c.camel@intel.com> (raw)
In-Reply-To: <179024882733.202880.3180124007422961682@61270ab9df2a>

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

On Thu, 2026-09-24 at 11:20 +0000, Patchwork wrote:
Patch Details
Series: Enable GSC loading and PXP for NVL-S
URL:    https://patchwork.freedesktop.org/series/174837/
State:  failure
Details:        https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-174837v1/index.html
CI Bug Log - changes from xe-5815-703cd271db3a35088460ab3fec0a96bd48e7fe04_FULL -> xe-pw-174837v1_FULL
Summary

FAILURE

Serious unknown changes coming with xe-pw-174837v1_FULL absolutely need to be
verified manually.

If you think the reported changes have nothing to do with the changes
introduced in xe-pw-174837v1_FULL, please notify your bug team (I915-ci-infra@lists.freedesktop.org) to allow them
to document this new failure mode, which will reduce false positives in CI.

Participating hosts (3 -> 3)

No changes in participating hosts

Possible new issues

Here are the unknown changes that may have been introduced in xe-pw-174837v1_FULL:

IGT changes
Possible regressions

  *   igt@xe_ccs@suspend-resume@tile64-compressed-compfmt0-system-system:
     *   shard-ptl: PASS<https://intel-gfx-ci.01.org/tree/intel-xe/xe-5815-703cd271db3a35088460ab3fec0a96bd48e7fe04/shard-ptl-8/igt@xe_ccs@suspend-resume@tile64-compressed-compfmt0-system-system.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-174837v1/shard-ptl-8/igt@xe_ccs@suspend-resume@tile64-compressed-compfmt0-system-system.html> +1 other test dmesg-warn

this failure is unrelated since the only changes in my series impacts NVL-S alone.

[-- Attachment #2: Type: text/html, Size: 2718 bytes --]

      reply	other threads:[~2026-09-29 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 18:36 [PATCH 0/2] Enable GSC loading and PXP for NVL-S Alan Previn
2026-09-23 18:36 ` [PATCH 1/2] drm/xe/gsc: Define GSC " Alan Previn
2026-09-29 19:18   ` Julia Filipchuk
2026-09-23 18:36 ` [PATCH 2/2] drm/xe/nvl-s: Enable PXP " Alan Previn
2026-09-29 19:18   ` Julia Filipchuk
2026-09-29 19:36     ` Rodrigo Vivi
2026-09-23 19:41 ` ✓ CI.KUnit: success for Enable GSC loading and " Patchwork
2026-09-23 21:39 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-24 11:20 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-29 18:24   ` Teres Alexis, Alan Previn [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=073cb12a539b63aed0e051d3c526cfe36b757a6c.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=intel-xe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox