Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	<I915-ci-infra@lists.freedesktop.org>,
	<intel-gfx@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for drm/i915/xe3lpd: Load DMC for xe3lpd 3002
Date: Mon, 20 Oct 2025 13:21:15 -0300	[thread overview]
Message-ID: <176097727514.3231.12260417256718718005@intel.com> (raw)
In-Reply-To: <176067186701.23602.14960783266679330247@97596180aaec>

Quoting Patchwork (2025-10-17 00:31:07-03:00)
>== Series Details ==
>
>Series: drm/i915/xe3lpd: Load DMC for xe3lpd 3002
>URL   : https://patchwork.freedesktop.org/series/156063/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_17375_full -> Patchwork_156063v1_full
>====================================================
>
>Summary
>-------
>
>  **FAILURE**
>
>  Serious unknown changes coming with Patchwork_156063v1_full absolutely need to be
>  verified manually.
>  
>  If you think the reported changes have nothing to do with the changes
>  introduced in Patchwork_156063v1_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 (11 -> 12)
>------------------------------
>
>  Additional (1): shard-snb-0 
>
>Possible new issues
>-------------------
>
>  Here are the unknown changes that may have been introduced in Patchwork_156063v1_full:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
>  * igt@kms_vblank@wait-forked-hang:
>    - shard-dg2-9:        NOTRUN -> [ABORT][1] +1 other test abort
>   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_156063v1/shard-dg2-9/igt@kms_vblank@wait-forked-hang.html
>
>  * igt@kms_vblank@wait-forked-hang@pipe-d-hdmi-a-2:
>    - shard-dg2-9:        NOTRUN -> [DMESG-FAIL][2]
>   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_156063v1/shard-dg2-9/igt@kms_vblank@wait-forked-hang@pipe-d-hdmi-a-2.html
>

None of those are on WCL, so they are unrelated to this patch.

--
Gustavo Sousa

  reply	other threads:[~2025-10-20 16:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 13:15 [PATCH] drm/i915/xe3lpd: Load DMC for xe3lpd 3002 Dnyaneshwar Bhadane
2025-10-16 19:19 ` ✓ i915.CI.BAT: success for " Patchwork
2025-10-17  3:31 ` ✗ i915.CI.Full: failure " Patchwork
2025-10-20 16:21   ` Gustavo Sousa [this message]
2025-10-17 10:38 ` [PATCH] " Borah, Chaitanya Kumar
2025-10-20 16:32 ` Gustavo Sousa
2025-10-20 17:05   ` 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=176097727514.3231.12260417256718718005@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=dnyaneshwar.bhadane@intel.com \
    --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