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: ✗ CI.FULL: failure for drm/xe/pf: Fix potential GGTT allocation leak
Date: Tue, 5 Nov 2024 15:48:16 +0100	[thread overview]
Message-ID: <de154074-6062-4735-8b70-5952bfd9bd28@intel.com> (raw)
In-Reply-To: <173076692070.1409781.8767785881855972471@2413ebb6fbb6>



On 05.11.2024 01:35, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/pf: Fix potential GGTT allocation leak
> URL   : https://patchwork.freedesktop.org/series/140881/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2159-0a6cc4357ae4d824f909468ca1deed28ae5ac96f_full -> xe-pw-140881v1_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-140881v1_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-140881v1_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-140881v1_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####

all unrelated, from non-SRIOV platforms

> 
>   * igt@kms_cursor_crc@cursor-suspend@pipe-a-edp-1:
>     - shard-lnl:          [PASS][1] -> [DMESG-WARN][2] +2 other tests dmesg-warn
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2159-0a6cc4357ae4d824f909468ca1deed28ae5ac96f/shard-lnl-5/igt@kms_cursor_crc@cursor-suspend@pipe-a-edp-1.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-140881v1/shard-lnl-5/igt@kms_cursor_crc@cursor-suspend@pipe-a-edp-1.html
> 
>   * igt@kms_cursor_edge_walk@256x256-top-bottom@pipe-a-edp-1:
>     - shard-lnl:          [PASS][3] -> [FAIL][4] +2 other tests fail
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2159-0a6cc4357ae4d824f909468ca1deed28ae5ac96f/shard-lnl-7/igt@kms_cursor_edge_walk@256x256-top-bottom@pipe-a-edp-1.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-140881v1/shard-lnl-3/igt@kms_cursor_edge_walk@256x256-top-bottom@pipe-a-edp-1.html
> 
>   * igt@kms_flip@2x-dpms-vs-vblank-race-interruptible:
>     - shard-dg2-set2:     NOTRUN -> [FAIL][5] +1 other test fail
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-140881v1/shard-dg2-434/igt@kms_flip@2x-dpms-vs-vblank-race-interruptible.html
> 
>   
> #### Warnings ####
> 
>   * igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
>     - shard-adlp:         [FAIL][6] ([Intel XE#1242]) -> [DMESG-FAIL][7]
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2159-0a6cc4357ae4d824f909468ca1deed28ae5ac96f/shard-adlp-1/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-140881v1/shard-adlp-2/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
> 
>   

      reply	other threads:[~2024-11-05 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 14:49 [PATCH] drm/xe/pf: Fix potential GGTT allocation leak Michal Wajdeczko
2024-11-04 16:13 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-04 16:13 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-04 16:15 ` ✓ CI.KUnit: success " Patchwork
2024-11-04 16:26 ` [PATCH] " Matthew Brost
2024-11-04 16:26 ` ✓ CI.Build: success for " Patchwork
2024-11-04 16:28 ` ✓ CI.Hooks: " Patchwork
2024-11-04 16:30 ` ✓ CI.checksparse: " Patchwork
2024-11-04 16:52 ` ✓ CI.BAT: " Patchwork
2024-11-05  0:35 ` ✗ CI.FULL: failure " Patchwork
2024-11-05 14:48   ` 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=de154074-6062-4735-8b70-5952bfd9bd28@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