From: Gustavo Sousa <gustavo.sousa@intel.com>
To: <I915-ci-infra@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for drm/xe/nvls: Update PCI IDs (rev3)
Date: Tue, 9 Jun 2026 13:47:06 -0300 [thread overview]
Message-ID: <87ldcnpsol.fsf@intel.com> (raw)
In-Reply-To: <178074350923.50863.6713229616353354808@6beec6c84f66>
Patchwork <patchwork@emeril.freedesktop.org> writes:
> == Series Details ==
>
> Series: drm/xe/nvls: Update PCI IDs (rev3)
> URL : https://patchwork.freedesktop.org/series/167043/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-5213-0ecb0a41cb32dfc7620a903629a6951ef1aaea52_FULL -> xe-pw-167043v3_FULL
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-167043v3_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-167043v3_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-167043v3_FULL:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_plane_multiple@2x-tiling-4@pipe-d-hdmi-a-3-pipe-c-dp-2:
> - shard-bmg: NOTRUN -> [FAIL][1] +1 other test fail
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-167043v3/shard-bmg-3/igt@kms_plane_multiple@2x-tiling-4@pipe-d-hdmi-a-3-pipe-c-dp-2.html
This patch only updates PCI IDs for NVL-S and, as such, this BMG failure
is unrelated.
--
Gustavo Sousa
prev parent reply other threads:[~2026-06-09 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 18:03 [PATCH] drm/xe/nvls: Update PCI IDs Gustavo Sousa
2026-05-21 18:38 ` ✓ CI.KUnit: success for " Patchwork
2026-05-21 19:31 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-21 22:18 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-22 5:38 ` [PATCH] " Bhadane, Dnyaneshwar
2026-06-09 17:02 ` Gustavo Sousa
2026-05-29 11:55 ` ✓ CI.KUnit: success for drm/xe/nvls: Update PCI IDs (rev2) Patchwork
2026-05-29 12:40 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-29 15:41 ` ✓ Xe.CI.FULL: " Patchwork
2026-06-05 21:00 ` ✓ CI.KUnit: success for drm/xe/nvls: Update PCI IDs (rev3) Patchwork
2026-06-05 21:42 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-06 10:58 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-09 16:47 ` Gustavo Sousa [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=87ldcnpsol.fsf@intel.com \
--to=gustavo.sousa@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--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