All of 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: ✗ i915.CI.Full: failure for Integrat kmemleak scans in igt_runner
Date: Wed, 22 Jan 2025 09:25:14 +0100	[thread overview]
Message-ID: <be67441d-74c4-4d24-afe6-e4f4bad1a121@linux.intel.com> (raw)
In-Reply-To: <173750861737.2837194.5013051827516821568@b555e5b46a47>

Dear I915,

On 22.01.2025 02:16, 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 IGT_8202_full -> IGTPW_12473_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_12473_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_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.
> 
>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/index.html
> 
> Participating hosts (11 -> 11)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_12473_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_madvise@dontneed-after-mmap:
>     - shard-dg2:          NOTRUN -> [ABORT][1]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-dg2-7/igt@gem_madvise@dontneed-after-mmap.html
> 
>   * igt@gem_workarounds@reset-fd:
>     - shard-mtlp:         NOTRUN -> [ABORT][2]
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-mtlp-4/igt@gem_workarounds@reset-fd.html
> 
>   * igt@i915_pm_rpm@system-suspend-execbuf:
>     - shard-rkl:          [PASS][3] -> [SKIP][4]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8202/shard-rkl-4/igt@i915_pm_rpm@system-suspend-execbuf.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-rkl-3/igt@i915_pm_rpm@system-suspend-execbuf.html
> 
>   * igt@kms_cursor_crc@cursor-onscreen-256x85@pipe-a-hdmi-a-2:
>     - shard-rkl:          NOTRUN -> [FAIL][5] +2 other tests fail
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-rkl-1/igt@kms_cursor_crc@cursor-onscreen-256x85@pipe-a-hdmi-a-2.html
> 
>   * igt@kms_cursor_crc@cursor-sliding-128x42@pipe-a-hdmi-a-2:
>     - shard-rkl:          [PASS][6] -> [FAIL][7] +1 other test fail
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8202/shard-rkl-1/igt@kms_cursor_crc@cursor-sliding-128x42@pipe-a-hdmi-a-2.html
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-rkl-1/igt@kms_cursor_crc@cursor-sliding-128x42@pipe-a-hdmi-a-2.html
> 
>   * igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions:
>     - shard-mtlp:         [PASS][8] -> [ABORT][9]
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8202/shard-mtlp-7/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions.html
>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-mtlp-2/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions.html
> 
>   * igt@kms_psr@psr2-no-drrs@edp-1:
>     - shard-mtlp:         NOTRUN -> [FAIL][10] +1 other test fail
>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-mtlp-2/igt@kms_psr@psr2-no-drrs@edp-1.html
> 
>   * igt@kms_vblank@ts-continuation-modeset-rpm@pipe-a-hdmi-a-1:
>     - shard-rkl:          NOTRUN -> [SKIP][11]
>    [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-rkl-2/igt@kms_vblank@ts-continuation-modeset-rpm@pipe-a-hdmi-a-1.html
> 
>   * igt@perf_pmu@busy-accuracy-2@vecs0:
>     - shard-mtlp:         [PASS][12] -> [FAIL][13] +1 other test fail
>    [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8202/shard-mtlp-6/igt@perf_pmu@busy-accuracy-2@vecs0.html
>    [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12473/shard-mtlp-3/igt@perf_pmu@busy-accuracy-2@vecs0.html

These are unrelated to my change. Please fix and rerun.

Thanks,

Peter

  reply	other threads:[~2025-01-22  8:25 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
2025-01-22  1:16 ` ✗ i915.CI.Full: " Patchwork
2025-01-22  8:25   ` Peter Senna Tschudin [this message]
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=be67441d-74c4-4d24-afe6-e4f4bad1a121@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.