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: ✗ i915.CI.Full: failure for Integrate kmemleak scans in igt_runner (rev5)
Date: Wed, 5 Mar 2025 08:44:46 +0100	[thread overview]
Message-ID: <3a204d60-598f-4c2f-95f0-85dea8ef2e08@linux.intel.com> (raw)
In-Reply-To: <174115973234.43.3968612023355278653@d1c082ef0712>

Dear i915,

On 05.03.2025 08:28, 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 CI_DRM_16199_full -> IGTPW_12677_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_12677_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_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.
> 
>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12677/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_12677_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_exec_big@single:
>     - shard-tglu:         NOTRUN -> [ABORT][1]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12677/shard-tglu-2/igt@gem_exec_big@single.html

This is unrelated. Please fix and re-run.

[...]

Thank you,

Peter

  reply	other threads:[~2025-03-05  7:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 10:18 [PATCH v7 i-g-t 0/3] Integrate kmemleak scans in igt_runner Peter Senna Tschudin
2025-02-27 10:18 ` [PATCH v7 i-g-t 1/3] runner/kmemleak: library to interact with kmemleak Peter Senna Tschudin
2025-02-28  7:04   ` Peter Senna Tschudin
2025-03-06 12:32     ` Kamil Konieczny
2025-03-07  3:59       ` vitaly prosyak
2025-03-06 12:02   ` Kamil Konieczny
2025-02-27 10:18 ` [PATCH v7 i-g-t 2/3] runner/executor: Integrate igt_kmemleak scans Peter Senna Tschudin
2025-02-28  7:05   ` Peter Senna Tschudin
2025-03-06 12:25   ` Kamil Konieczny
2025-02-27 10:18 ` [PATCH v7 i-g-t 3/3] scripts/run-tests.sh: Add support to kmemleak reports and igt_facts Peter Senna Tschudin
2025-02-28  7:07   ` Peter Senna Tschudin
2025-02-28  3:56 ` ✓ Xe.CI.BAT: success for Integrate kmemleak scans in igt_runner (rev5) Patchwork
2025-02-28  4:28 ` ✓ i915.CI.BAT: " Patchwork
2025-02-28  8:37 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-28  9:06   ` Peter Senna Tschudin
2025-02-28 11:53     ` Ravali, JupallyX
2025-03-05  7:28 ` ✗ i915.CI.Full: " Patchwork
2025-03-05  7:44   ` Peter Senna Tschudin [this message]
2025-03-05 16:12     ` Illipilli, TejasreeX

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=3a204d60-598f-4c2f-95f0-85dea8ef2e08@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