All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: <igt-dev@lists.freedesktop.org>,
	Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
	<I915-ci-infra@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.BAT: failure for tools/intel_gpu_top: prevent losing original pointer on realloc failure
Date: Wed, 17 Dec 2025 07:33:32 +0100	[thread overview]
Message-ID: <DF0A625OYMPE.R96VEDAV0KCI@intel.com> (raw)
In-Reply-To: <176583629876.91286.13557144638544501813@a3b018990fe9>

Hi CI team,

On Mon Dec 15, 2025 at 11:04 PM CET, Patchwork wrote:
> == Series Details ==
>
> Series: tools/intel_gpu_top: prevent losing original pointer on realloc failure
> URL   : https://patchwork.freedesktop.org/series/159023/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from IGT_8666 -> IGTPW_14211
> ====================================================
>
> Summary
> -------
>
>   **FAILURE**
>
>   Serious unknown changes coming with IGTPW_14211 absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_14211, 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_14211/index.html
>
> Participating hosts (43 -> 41)
> ------------------------------
>
>   Missing    (2): bat-dg2-13 fi-snb-2520m 
>
> Possible new issues
> -------------------
>
>   Here are the unknown changes that may have been introduced in IGTPW_14211:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
>   * igt@i915_selftest@live@objects:
>     - bat-arlh-3:         [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8666/bat-arlh-3/igt@i915_selftest@live@objects.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_14211/bat-arlh-3/igt@i915_selftest@live@objects.html
>
These failures are unrelated to the patch changes.

Best regards,
Sebastian


  reply	other threads:[~2025-12-17  6:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 14:45 [PATCH i-g-t] tools/intel_gpu_top: prevent losing original pointer on realloc failure Sebastian Brzezinka
2025-12-15 22:04 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-12-17  6:33   ` Sebastian Brzezinka [this message]
2025-12-15 22:28 ` ✗ Xe.CI.BAT: " Patchwork
2025-12-16  7:18 ` [PATCH i-g-t] " Krzysztof Karas
2025-12-16 17:29   ` Kamil Konieczny
2025-12-16  8:16 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-12-16 19:02 ` [PATCH i-g-t] " Tvrtko Ursulin
2025-12-17  7:05   ` Sebastian Brzezinka
2025-12-17 10:07     ` Tvrtko Ursulin

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=DF0A625OYMPE.R96VEDAV0KCI@intel.com \
    --to=sebastian.brzezinka@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.