From: Imre Deak <imre.deak@intel.com>
To: <I915-ci-infra@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.BAT: failure for series starting with [1/2] drm/i915/ddi: Fix cleanup after DP connector init failure
Date: Fri, 8 May 2026 13:10:39 +0300 [thread overview]
Message-ID: <af22nzAuYol9aTjz@ideak-desk.lan> (raw)
In-Reply-To: <177815149034.47093.7459984050326362958@5ab824fced77>
Hi CI team,
could you forward this patchset for getting a full test coverage?
The BAT failure is unrelated to the changes, see below.
On Thu, May 07, 2026 at 10:58:10AM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/2] drm/i915/ddi: Fix cleanup after DP connector init failure
> URL : https://patchwork.freedesktop.org/series/166105/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_18438 -> Patchwork_166105v1
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_166105v1 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_166105v1, 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_166105v1/index.html
>
> Participating hosts (42 -> 40)
> ------------------------------
>
> Missing (2): bat-dg2-13 fi-snb-2520m
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_166105v1:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@i915_selftest@live@gt_lrc:
> - bat-mtlp-9: [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18438/bat-mtlp-9/igt@i915_selftest@live@gt_lrc.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_166105v1/bat-mtlp-9/igt@i915_selftest@live@gt_lrc.html
The changes in the patchset affect only error scenarios during DP/HDMI
connector registration, however there wasn't any such error occuring in
the above test run: both in the PASS and INCOMPLETE case
eDP-1/DP-1..5/HDMI-A-1 are registered without any errors.
> Known issues
> ------------
>
> Here are the changes found in Patchwork_166105v1 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@i915_selftest@live:
> - bat-dg2-8: [PASS][3] -> [DMESG-FAIL][4] ([i915#12061]) +1 other test dmesg-fail
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18438/bat-dg2-8/igt@i915_selftest@live.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_166105v1/bat-dg2-8/igt@i915_selftest@live.html
>
>
> [i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_18438 -> Patchwork_166105v1
>
> CI-20190529: 20190529
> CI_DRM_18438: 30f8a0629f6924f24369cac9161b1a9741880259 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_8899: 3e5747e536f148bf232049e49a00e2b683f91a83 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Patchwork_166105v1: 30f8a0629f6924f24369cac9161b1a9741880259 @ git://anongit.freedesktop.org/gfx-ci/linux
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_166105v1/index.html
next prev parent reply other threads:[~2026-05-08 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 6:59 [PATCH 1/2] drm/i915/ddi: Fix cleanup after DP connector init failure Imre Deak
2026-05-07 6:59 ` [PATCH 2/2] drm/i915/ddi: Fix cleanup after HDMI " Imre Deak
2026-05-08 14:29 ` Hogander, Jouni
2026-05-08 14:34 ` Imre Deak
2026-05-07 10:58 ` ✗ i915.CI.BAT: failure for series starting with [1/2] drm/i915/ddi: Fix cleanup after DP " Patchwork
2026-05-08 10:10 ` Imre Deak [this message]
2026-05-08 12:26 ` [PATCH 1/2] " Hogander, Jouni
2026-05-08 12:38 ` Imre Deak
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=af22nzAuYol9aTjz@ideak-desk.lan \
--to=imre.deak@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