Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: <I915-ci-infra@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for drm/i915/bw: Split bandwidth params into platform- and display-IP-specific structs (rev4)
Date: Tue, 19 May 2026 10:45:51 -0300	[thread overview]
Message-ID: <87zf1vpl68.fsf@intel.com> (raw)
In-Reply-To: <177917681954.84521.3965728903623704285@5ab824fced77>

Patchwork <patchwork@emeril.freedesktop.org> writes:

> == Series Details ==
>
> Series: drm/i915/bw: Split bandwidth params into platform- and display-IP-specific structs (rev4)
> URL   : https://patchwork.freedesktop.org/series/164567/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_18509_full -> Patchwork_164567v4_full
> ====================================================
>
> Summary
> -------
>
>   **FAILURE**
>
>   Serious unknown changes coming with Patchwork_164567v4_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_164567v4_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 (10 -> 10)
> ------------------------------
>
>   No changes in participating hosts
>
> Possible new issues
> -------------------
>
>   Here are the unknown changes that may have been introduced in Patchwork_164567v4_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
>   * igt@kms_flip@plain-flip-fb-recreate-interruptible@a-vga1:
>     - shard-snb:          [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18509/shard-snb4/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-vga1.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_164567v4/shard-snb7/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-vga1.html

This is an unrelated failure: SNB has display version 6 and, as such, is
not affected by this series.

--
Gustavo Sousa

  reply	other threads:[~2026-05-19 13:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 16:13 [PATCH v4 0/5] drm/i915/bw: Split bandwidth params into platform- and display-IP-specific structs Gustavo Sousa
2026-05-18 16:14 ` [PATCH v4 1/5] drm/i915/bw: Don't call intel_dram_info() too early Gustavo Sousa
2026-05-18 16:14 ` [PATCH v4 2/5] drm/i915/bw: Extract platform-specific parameters Gustavo Sousa
2026-05-18 16:46   ` Matt Roper
2026-05-18 16:14 ` [PATCH v4 3/5] drm/i915/bw: Deduplicate intel_sa_info instances Gustavo Sousa
2026-05-18 16:14 ` [PATCH v4 4/5] drm/i915/bw: Rename struct intel_sa_info to intel_display_bw_params Gustavo Sousa
2026-05-18 16:14 ` [PATCH v4 5/5] drm/i915/bw: Extract get_display_bw_params() Gustavo Sousa
2026-05-18 16:56   ` Matt Roper
2026-05-18 17:57 ` ✓ i915.CI.BAT: success for drm/i915/bw: Split bandwidth params into platform- and display-IP-specific structs (rev4) Patchwork
2026-05-19  7:46 ` ✗ i915.CI.Full: failure " Patchwork
2026-05-19 13:45   ` Gustavo Sousa [this message]
2026-05-19 18:00 ` [PATCH v4 0/5] drm/i915/bw: Split bandwidth params into platform- and display-IP-specific structs Gustavo Sousa

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=87zf1vpl68.fsf@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=intel-gfx@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