Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for VF: debugfs fixes (rev2)
Date: Fri, 11 Apr 2025 12:12:50 +0200	[thread overview]
Message-ID: <782597eb-4895-4db7-a075-4947c4ffef43@intel.com> (raw)
In-Reply-To: <174376403057.38353.2093768642685836501@e6b6f09ec485>



On 04.04.2025 12:53, Patchwork wrote:
> == Series Details ==
> 
> Series: VF: debugfs fixes (rev2)
> URL   : https://patchwork.freedesktop.org/series/146561/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2903-9edc6ea87f86cbb6cda6b76d334c07492d0a8073_FULL -> xe-pw-146561v2_FULL
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-146561v2_FULL absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-146561v2_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 (4 -> 4)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-pw-146561v2_FULL:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_plane_multiple@tiling-4@pipe-a-edp-1:
>     - shard-lnl:          [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2903-9edc6ea87f86cbb6cda6b76d334c07492d0a8073/shard-lnl-1/igt@kms_plane_multiple@tiling-4@pipe-a-edp-1.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146561v2/shard-lnl-6/igt@kms_plane_multiple@tiling-4@pipe-a-edp-1.html

it must be an unrelated CI/KMS glitch

https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146561v2/shard-lnl-6/dmesg18.txt

<7>[  453.334556] [IGT] kms_plane_multiple: finished subtest
pipe-A-eDP-1, SUCCESS


      reply	other threads:[~2025-04-11 10:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03 14:26 [PATCH v2 0/3] VF: debugfs fixes Michal Wajdeczko
2025-04-03 14:26 ` [PATCH v2 1/3] drm/xe/guc: Refactor GuC debugfs initialization Michal Wajdeczko
2025-04-10 17:20   ` Lucas De Marchi
2025-04-03 14:26 ` [PATCH v2 2/3] drm/xe/guc: Don't expose GuC privileged debugfs files if VF Michal Wajdeczko
2025-04-10 17:21   ` Lucas De Marchi
2025-04-03 14:26 ` [PATCH v2 3/3] drm/xe/vf: Don't expose privileged GT " Michal Wajdeczko
2025-04-03 20:28   ` Matthew Brost
2025-04-03 20:56     ` Michal Wajdeczko
2025-04-03 21:30       ` Matthew Brost
2025-04-09 10:29   ` Bernatowicz, Marcin
2025-04-10 17:22   ` Lucas De Marchi
2025-04-03 18:43 ` ✓ CI.Patch_applied: success for VF: debugfs fixes (rev2) Patchwork
2025-04-03 18:44 ` ✓ CI.checkpatch: " Patchwork
2025-04-03 18:45 ` ✓ CI.KUnit: " Patchwork
2025-04-03 19:01 ` ✓ CI.Build: " Patchwork
2025-04-03 19:04 ` ✓ CI.Hooks: " Patchwork
2025-04-03 19:05 ` ✓ CI.checksparse: " Patchwork
2025-04-04  0:24 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-04  4:52 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-04 10:53 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-11 10:12   ` Michal Wajdeczko [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=782597eb-4895-4db7-a075-4947c4ffef43@intel.com \
    --to=michal.wajdeczko@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