Re: ✗ Xe.CI.Full: failure for Integrate kmemleak scans in igt_runner (rev5)

[Peter Senna Tschudin <peter.senna@linux.intel.com>]

Dear I915,

On 28.02.2025 09:37, Patchwork wrote:
> == Series Details ==
> 
> Series: Integrate kmemleak scans in igt_runner (rev5)
> URL   : https://patchwork.freedesktop.org/series/143996/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from XEIGT_8251_full -> XEIGTPW_12677_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with XEIGTPW_12677_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in XEIGTPW_12677_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 XEIGTPW_12677_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_cdclk@mode-transition-all-outputs:
>     - shard-dg2-set2:     NOTRUN -> [SKIP][1]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12677/shard-dg2-464/igt@kms_cdclk@mode-transition-all-outputs.html
> 
>   * igt@kms_plane_lowres@tiling-none:
>     - shard-dg2-set2:     NOTRUN -> [DMESG-WARN][2]
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12677/shard-dg2-436/igt@kms_plane_lowres@tiling-none.html
> 
>   * igt@xe_vm@large-binds-2147483648:
>     - shard-dg2-set2:     [PASS][3] -> [DMESG-WARN][4]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8251/shard-dg2-432/igt@xe_vm@large-binds-2147483648.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12677/shard-dg2-434/igt@xe_vm@large-binds-2147483648.html
> 

These are unrelated to my change. Please fix and re-run.

Thank you,

Peter

[...]