Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for Integrat kmemleak scans in igt_runner
Date: Wed, 22 Jan 2025 09:23:47 +0100	[thread overview]
Message-ID: <69a971ce-3503-4119-ae7a-d6b66322ff0a@linux.intel.com> (raw)
In-Reply-To: <173748418205.2687243.16683826694177507557@b555e5b46a47>

Dear I915,

On 21.01.2025 19:29, Patchwork wrote:
> == Series Details ==
> 
> Series: Integrat kmemleak scans in igt_runner
> URL   : https://patchwork.freedesktop.org/series/143791/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from XEIGT_8202_full -> XEIGTPW_12473_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with XEIGTPW_12473_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in XEIGTPW_12473_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_12473_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@core_setmaster@master-drop-set-root:
>     - shard-bmg:          [PASS][1] -> [FAIL][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-bmg-8/igt@core_setmaster@master-drop-set-root.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-bmg-3/igt@core_setmaster@master-drop-set-root.html
> 
>   * igt@kms_flip@2x-plain-flip-ts-check@bd-dp2-hdmi-a3:
>     - shard-bmg:          [PASS][3] -> [INCOMPLETE][4] +2 other tests incomplete
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-bmg-8/igt@kms_flip@2x-plain-flip-ts-check@bd-dp2-hdmi-a3.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-bmg-7/igt@kms_flip@2x-plain-flip-ts-check@bd-dp2-hdmi-a3.html
> 
>   * igt@kms_flip@plain-flip-ts-check-interruptible@d-hdmi-a3:
>     - shard-bmg:          [PASS][5] -> [DMESG-WARN][6] +51 other tests dmesg-warn
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-bmg-1/igt@kms_flip@plain-flip-ts-check-interruptible@d-hdmi-a3.html
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-bmg-3/igt@kms_flip@plain-flip-ts-check-interruptible@d-hdmi-a3.html
> 
>   * igt@kms_hdr@bpc-switch-suspend:
>     - shard-dg2-set2:     [PASS][7] -> [DMESG-WARN][8] +1 other test dmesg-warn
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-dg2-463/igt@kms_hdr@bpc-switch-suspend.html
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-dg2-436/igt@kms_hdr@bpc-switch-suspend.html
> 
>   * igt@xe_gt_freq@freq_suspend:
>     - shard-dg2-set2:     [PASS][9] -> [INCOMPLETE][10]
>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-dg2-435/igt@xe_gt_freq@freq_suspend.html
>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-dg2-466/igt@xe_gt_freq@freq_suspend.html
> 
>   
> #### Warnings ####
> 
>   * igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-mc-ccs:
>     - shard-dg2-set2:     [DMESG-WARN][11] ([Intel XE#1033]) -> [DMESG-WARN][12]
>    [11]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-dg2-433/igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-mc-ccs.html
>    [12]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-dg2-466/igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-mc-ccs.html
> 
>   * igt@kms_dirtyfb@fbc-dirtyfb-ioctl:
>     - shard-bmg:          [SKIP][13] ([Intel XE#2136] / [Intel XE#2231]) -> [SKIP][14]
>    [13]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-bmg-1/igt@kms_dirtyfb@fbc-dirtyfb-ioctl.html
>    [14]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-bmg-7/igt@kms_dirtyfb@fbc-dirtyfb-ioctl.html
> 
>   * igt@kms_flip@plain-flip-ts-check-interruptible:
>     - shard-bmg:          [FAIL][15] ([Intel XE#2882]) -> [DMESG-WARN][16]
>    [15]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-bmg-1/igt@kms_flip@plain-flip-ts-check-interruptible.html
>    [16]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-bmg-3/igt@kms_flip@plain-flip-ts-check-interruptible.html
> 
>   * igt@kms_pm_rpm@drm-resources-equal:
>     - shard-bmg:          [SKIP][17] ([Intel XE#2446]) -> [DMESG-WARN][18]
>    [17]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8202/shard-bmg-1/igt@kms_pm_rpm@drm-resources-equal.html
>    [18]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12473/shard-bmg-2/igt@kms_pm_rpm@drm-resources-equal.html

These are unrelated to my change. Can you fix and re-run?

  reply	other threads:[~2025-01-22  8:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 11:29 [PATCH i-g-t 0/2] Integrat kmemleak scans in igt_runner Peter Senna Tschudin
2025-01-21 11:29 ` [PATCH i-g-t 1/2] lib/igt_kmemleak: library to interact with kmemleak Peter Senna Tschudin
2025-01-22 17:09   ` Cavitt, Jonathan
2025-01-27 11:19     ` Peter Senna Tschudin
2025-01-27 16:28       ` Cavitt, Jonathan
2025-01-21 11:29 ` [PATCH i-g-t 2/2] runner/executor: Integrate igt_kmemleak scans Peter Senna Tschudin
2025-01-22 18:18   ` Cavitt, Jonathan
2025-01-27 11:05     ` Peter Senna Tschudin
2025-01-27 15:44       ` Cavitt, Jonathan
2025-01-21 12:20 ` ✗ GitLab.Pipeline: warning for Integrat kmemleak scans in igt_runner Patchwork
2025-01-22  8:22   ` Peter Senna Tschudin
2025-01-21 12:58 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-21 13:54 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-21 18:29 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-22  8:23   ` Peter Senna Tschudin [this message]
2025-01-22  1:16 ` ✗ i915.CI.Full: " Patchwork
2025-01-22  8:25   ` Peter Senna Tschudin
2025-01-22 11:36     ` Ravali, JupallyX
2025-01-22 10:47 ` ✓ i915.CI.Full: success " Patchwork
2025-01-27 10:53 ` [PATCH i-g-t v2 0/2] Integrate " Peter Senna Tschudin
2025-01-27 10:53   ` [PATCH i-g-t v2 1/2] lib/igt_kmemleak: library to interact with kmemleak Peter Senna Tschudin
2025-01-27 10:53   ` [PATCH i-g-t v2 2/2] runner/executor: Integrate igt_kmemleak scans Peter Senna Tschudin
2025-01-27 15:28 ` [PATCH i-g-t v3 0/2] Integrate kmemleak scans in igt_runner Peter Senna Tschudin
2025-01-27 15:28   ` [PATCH i-g-t v3 1/2] lib/igt_kmemleak: library to interact with kmemleak Peter Senna Tschudin
2025-01-27 16:38     ` Cavitt, Jonathan
2025-01-27 17:07       ` Peter Senna Tschudin
2025-01-27 18:43         ` Cavitt, Jonathan
2025-01-27 15:28   ` [PATCH i-g-t v2 resend 2/2] runner/executor: Integrate igt_kmemleak scans Peter Senna Tschudin
2025-01-27 15:47     ` Cavitt, Jonathan

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=69a971ce-3503-4119-ae7a-d6b66322ff0a@linux.intel.com \
    --to=peter.senna@linux.intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=igt-dev@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