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>, <intel-gfx@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.BAT: failure for drm/i915/dmc_wl: Do not check for DMC payload
Date: Mon, 27 Jan 2025 10:31:09 -0300	[thread overview]
Message-ID: <173798466909.2736.18370419027586461001@intel.com> (raw)
In-Reply-To: <173775376198.3232.56473874925376161@b555e5b46a47>

Quoting Patchwork (2025-01-24 18:22:41-03:00)
>== Series Details ==
>
>Series: drm/i915/dmc_wl: Do not check for DMC payload
>URL   : https://patchwork.freedesktop.org/series/143951/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_16018 -> Patchwork_143951v1
>====================================================
>
>Summary
>-------
>
>  **FAILURE**
>
>  Serious unknown changes coming with Patchwork_143951v1 absolutely need to be
>  verified manually.
>  
>  If you think the reported changes have nothing to do with the changes
>  introduced in Patchwork_143951v1, 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/Patchwork_143951v1/index.html
>
>Participating hosts (38 -> 37)
>------------------------------
>
>  Missing    (1): fi-snb-2520m 
>
>Possible new issues
>-------------------
>
>  Here are the unknown changes that may have been introduced in Patchwork_143951v1:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
>  * igt@kms_pm_rpm@basic-rte:
>    - bat-apl-1:          [PASS][1] -> [DMESG-WARN][2]
>   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16018/bat-apl-1/igt@kms_pm_rpm@basic-rte.html
>   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_143951v1/bat-apl-1/igt@kms_pm_rpm@basic-rte.html

Hi CI Team,

DMC wakelock is not exercised for this platform. This should not be
related to this patch.

Could you please re-report?

--
Gustavo Sousa

  reply	other threads:[~2025-01-27 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 19:12 [PATCH] drm/i915/dmc_wl: Do not check for DMC payload Gustavo Sousa
2025-01-24 21:22 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-01-27 13:31   ` Gustavo Sousa [this message]
2025-01-28  5:11     ` Ravali, JupallyX
2025-01-28  4:56 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-30  9:41 ` [PATCH] " Luca Coelho
2025-01-30 12:58 ` ✓ i915.CI.BAT: success for drm/i915/dmc_wl: Do not check for DMC payload (rev2) Patchwork
2025-01-30 14:18 ` [PATCH] drm/i915/dmc_wl: Do not check for DMC payload Krzysztof Karas
2025-01-31 20:16   ` Gustavo Sousa
2025-01-31 23:49     ` Lucas De Marchi
2025-02-03 11:44       ` Gustavo Sousa
2025-02-05  9:07         ` Krzysztof Karas
2025-01-30 14:50 ` ✗ i915.CI.Full: failure for drm/i915/dmc_wl: Do not check for DMC payload (rev2) Patchwork
2025-02-05 11:46   ` Gustavo Sousa
2025-02-05 14:18 ` [PATCH] drm/i915/dmc_wl: Do not check for DMC payload 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=173798466909.2736.18370419027586461001@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