Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Julia Filipchuk" <julia.filipchuk@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ Xe.CI.BAT: failure for drm/xe/guc: Test GuC v70.64.0 for BMG, LNL, PTL (rev2)
Date: Thu, 23 Apr 2026 01:05:23 -0000	[thread overview]
Message-ID: <177690632335.62.6821210803213708239@5ab824fced77> (raw)
In-Reply-To: <20260422212304.2250771-2-julia.filipchuk@intel.com>

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

== Series Details ==

Series: drm/xe/guc: Test GuC v70.64.0 for BMG, LNL, PTL (rev2)
URL   : https://patchwork.freedesktop.org/series/165316/
State : failure

== Summary ==

CI Bug Log - changes from xe-4927-9917a06970fd6775b7b4259be6cca21cb4e2b165_BAT -> xe-pw-165316v2_BAT
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with xe-pw-165316v2_BAT absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in xe-pw-165316v2_BAT, 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 (13 -> 13)
------------------------------

  No changes in participating hosts

Possible new issues
-------------------

  Here are the unknown changes that may have been introduced in xe-pw-165316v2_BAT:

### IGT changes ###

#### Possible regressions ####

  * igt@kms_pipe_crc_basic@hang-read-crc@pipe-c-hdmi-a-3:
    - bat-bmg-1:          [PASS][1] -> [DMESG-WARN][2] +4 other tests dmesg-warn
   [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4927-9917a06970fd6775b7b4259be6cca21cb4e2b165/bat-bmg-1/igt@kms_pipe_crc_basic@hang-read-crc@pipe-c-hdmi-a-3.html
   [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-165316v2/bat-bmg-1/igt@kms_pipe_crc_basic@hang-read-crc@pipe-c-hdmi-a-3.html

  * igt@xe_live_ktest@xe_bo:
    - bat-bmg-2:          [PASS][3] -> [DMESG-WARN][4] +1 other test dmesg-warn
   [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4927-9917a06970fd6775b7b4259be6cca21cb4e2b165/bat-bmg-2/igt@xe_live_ktest@xe_bo.html
   [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-165316v2/bat-bmg-2/igt@xe_live_ktest@xe_bo.html

  
Known issues
------------

  Here are the changes found in xe-pw-165316v2_BAT that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@sriov_basic@enable-vfs-autoprobe-off@numvfs-all:
    - bat-bmg-1:          [PASS][5] -> [ABORT][6] ([Intel XE#6652]) +1 other test abort
   [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4927-9917a06970fd6775b7b4259be6cca21cb4e2b165/bat-bmg-1/igt@sriov_basic@enable-vfs-autoprobe-off@numvfs-all.html
   [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-165316v2/bat-bmg-1/igt@sriov_basic@enable-vfs-autoprobe-off@numvfs-all.html

  
  [Intel XE#6652]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6652


Build changes
-------------

  * Linux: xe-4927-9917a06970fd6775b7b4259be6cca21cb4e2b165 -> xe-pw-165316v2

  IGT_8870: 1aba4b364b6dbdf7926cc78501e7281d5176b029 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  xe-4927-9917a06970fd6775b7b4259be6cca21cb4e2b165: 9917a06970fd6775b7b4259be6cca21cb4e2b165
  xe-pw-165316v2: 165316v2

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-165316v2/index.html

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

  parent reply	other threads:[~2026-04-23  1:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 21:23 [PATCH] drm/xe/guc: Test GuC v70.64.0 for BMG, LNL, PTL Julia Filipchuk
2026-04-22 23:36 ` ✓ CI.KUnit: success for drm/xe/guc: Test GuC v70.64.0 for BMG, LNL, PTL (rev2) Patchwork
2026-04-23  1:05 ` Patchwork [this message]
2026-04-23  9:34 ` ✗ Xe.CI.FULL: failure " 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=177690632335.62.6821210803213708239@5ab824fced77 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=julia.filipchuk@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