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 Integrate kmemleak scans in igt_runner (rev6)
Date: Sat, 8 Mar 2025 08:48:50 +0100 [thread overview]
Message-ID: <bb67e199-1a8b-4051-a76c-8dd168793feb@linux.intel.com> (raw)
In-Reply-To: <174139828756.4949.16053114640855089800@18a75f3d1eae>
Dear I915,
On 08.03.2025 02:44, Patchwork wrote:
> == Series Details ==
>
> Series: Integrate kmemleak scans in igt_runner (rev6)
> URL : https://patchwork.freedesktop.org/series/143996/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from IGT_8265_full -> IGTPW_12726_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_12726_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_12726_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_12726/index.html
>
> Participating hosts (10 -> 10)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_12726_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_mmap_offset@mmap-unmap@smem0:
> - shard-snb: [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8265/shard-snb2/igt@gem_mmap_offset@mmap-unmap@smem0.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12726/shard-snb4/igt@gem_mmap_offset@mmap-unmap@smem0.html
>
> * igt@i915_pm_rpm@debugfs-read:
> - shard-rkl: [PASS][3] -> [SKIP][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8265/shard-rkl-7/igt@i915_pm_rpm@debugfs-read.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12726/shard-rkl-4/igt@i915_pm_rpm@debugfs-read.html
>
> * igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a:
> - shard-rkl: [PASS][5] -> [INCOMPLETE][6] +1 other test incomplete
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8265/shard-rkl-3/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12726/shard-rkl-5/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a.html
>
These are unrelated. Please re-run.
Thank you,
Peter
[...]
next prev parent reply other threads:[~2025-03-08 7:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 9:34 [PATCH v8 i-g-t 0/3] Integrate kmemleak scans in igt_runner Peter Senna Tschudin
2025-03-07 9:34 ` [PATCH v8 i-g-t 1/3] runner/kmemleak: library to interact with kmemleak Peter Senna Tschudin
2025-03-10 10:37 ` Kamil Konieczny
2025-03-07 9:34 ` [PATCH v8 i-g-t 2/3] runner/executor: Integrate igt_kmemleak scans Peter Senna Tschudin
2025-03-07 9:34 ` [PATCH v8 i-g-t 3/3] scripts/run-tests.sh: Add support to kmemleak and igt_facts Peter Senna Tschudin
2025-03-10 3:07 ` vitaly prosyak
2025-03-10 7:07 ` Peter Senna Tschudin
2025-03-10 20:05 ` vitaly prosyak
2025-03-12 22:35 ` vitaly prosyak
2025-03-17 8:43 ` Peter Senna Tschudin
2025-03-18 0:28 ` vitaly prosyak
2025-03-07 23:55 ` ✓ Xe.CI.BAT: success for Integrate kmemleak scans in igt_runner (rev6) Patchwork
2025-03-08 0:14 ` ✓ i915.CI.BAT: " Patchwork
2025-03-08 1:44 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-08 7:48 ` Peter Senna Tschudin [this message]
2025-03-10 16:17 ` Ravali, JupallyX
2025-03-09 10:52 ` ✗ Xe.CI.Full: " Patchwork
2025-03-10 7:01 ` Peter Senna Tschudin
2025-03-10 11:05 ` [PATCH v8 i-g-t 0/3] Integrate kmemleak scans in igt_runner Kamil Konieczny
2025-03-10 16:14 ` ✓ i915.CI.Full: success for Integrate kmemleak scans in igt_runner (rev6) Patchwork
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=bb67e199-1a8b-4051-a76c-8dd168793feb@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.