public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Kolakowski, Jakub1" <jakub1.kolakowski@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for drm/xe/sriov: Mark NVL as SR-IOV capable
Date: Tue, 7 Apr 2026 12:48:25 +0200	[thread overview]
Message-ID: <7a2aba65-6eb9-4be0-b2a3-521b3d562bac@intel.com> (raw)
In-Reply-To: <177499435362.419941.17654559036249635909@a3b018990fe9>

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


On 3/31/2026 11:59 PM, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* 	drm/xe/sriov: Mark NVL as SR-IOV capable
> *URL:* 	https://patchwork.freedesktop.org/series/164174/
> *State:* 	failure
> *Details:* 
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164174v1/index.html
>
>
>   CI Bug Log - changes from
>   xe-4827-779129c7868f4c7205901d6e57b25de52b411d1c_FULL ->
>   xe-pw-164174v1_FULL
>
>
>     Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-164174v1_FULL absolutely 
> need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-164174v1_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 (2 -> 2)
>
> No changes in participating hosts
>
>
>     Possible new issues
>
> Here are the unknown changes that may have been introduced in 
> xe-pw-164174v1_FULL:
>
>
>       IGT changes
>
>
>         Possible regressions
>
>   * igt@xe_fault_injection@inject-fault-probe-function-xe_guc_ct_init:
>       o shard-lnl: PASS
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4827-779129c7868f4c7205901d6e57b25de52b411d1c/shard-lnl-2/igt@xe_fault_injection@inject-fault-probe-function-xe_guc_ct_init.html>
>         -> ABORT
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164174v1/shard-lnl-2/igt@xe_fault_injection@inject-fault-probe-function-xe_guc_ct_init.html>
>
this patch doesn't relate to LNL so the abort is unrelated to this change

>  *
>
>
>     Known issues
>
> Here are the changes found in xe-pw-164174v1_FULL that come from known 
> issues:
>
>
>       IGT changes
>
>
>         Issues hit
>
>  *
>
>     igt@kms_flip@flip-vs-expired-vblank-interruptible:
>
>       o shard-lnl: PASS
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4827-779129c7868f4c7205901d6e57b25de52b411d1c/shard-lnl-4/igt@kms_flip@flip-vs-expired-vblank-interruptible.html>
>         -> FAIL
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164174v1/shard-lnl-2/igt@kms_flip@flip-vs-expired-vblank-interruptible.html>
>         (Intel XE#301
>         <https://gitlab.freedesktop.org/drm/xe/kernel/issues/301>) +1
>         other test fail
>  *
>
>     igt@kms_vrr@seamless-rr-switch-virtual@pipe-a-edp-1:
>
>       o shard-lnl: PASS
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4827-779129c7868f4c7205901d6e57b25de52b411d1c/shard-lnl-6/igt@kms_vrr@seamless-rr-switch-virtual@pipe-a-edp-1.html>
>         -> FAIL
>         <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164174v1/shard-lnl-4/igt@kms_vrr@seamless-rr-switch-virtual@pipe-a-edp-1.html>
>         (Intel XE#2142
>         <https://gitlab.freedesktop.org/drm/xe/kernel/issues/2142>) +1
>         other test fail
>
>
>     Build changes
>
>   * Linux: xe-4827-779129c7868f4c7205901d6e57b25de52b411d1c ->
>     xe-pw-164174v1
>
> IGT_8839: 8839
> xe-4827-779129c7868f4c7205901d6e57b25de52b411d1c: 
> 779129c7868f4c7205901d6e57b25de52b411d1c
> xe-pw-164174v1: 164174v1
>

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

  reply	other threads:[~2026-04-07 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 15:22 [PATCH] drm/xe/sriov: Mark NVL as SR-IOV capable Jakub Kolakowski
2026-03-31 15:44 ` ✓ CI.KUnit: success for " Patchwork
2026-03-31 16:40 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-31 21:59 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-07 10:48   ` Kolakowski, Jakub1 [this message]
2026-03-31 22:07 ` [PATCH] " Matt Roper

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=7a2aba65-6eb9-4be0-b2a3-521b3d562bac@intel.com \
    --to=jakub1.kolakowski@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