From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Sumit Kishore <sumit.kishore@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <karthik.b.s@intel.com>
Subject: Re: [PATCH i-g-t] tests/kms_plane_alpha_blend: Print reason for test skips
Date: Wed, 25 Mar 2026 15:59:51 +0530 [thread overview]
Message-ID: <4f64f6c8-d3b0-4de1-8db7-16a37dbc6267@intel.com> (raw)
In-Reply-To: <20260325095952.316174-1-sumit.kishore@intel.com>
Hi Sumit,
On 25-03-2026 03:29 pm, Sumit Kishore wrote:
> From: sumit kishore <sumit.kishore@intel.com>
>
> Print debug message when tests are skipping on headless display systems.
Update subj and commit message. No debug message is being added in the
patch.
>
> v2: Add igt_display_require_output. [Karthik]
>
> Signed-off-by: sumit kishore <sumit.kishore@intel.com>
> ---
> tests/kms_plane_alpha_blend.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/kms_plane_alpha_blend.c b/tests/kms_plane_alpha_blend.c
> index 3a67dd8cd..3a2649833 100644
> --- a/tests/kms_plane_alpha_blend.c
> +++ b/tests/kms_plane_alpha_blend.c
> @@ -764,6 +764,9 @@ int igt_main_args("e", NULL, help_str, opt_handler, NULL)
> igt_display_require(&data.display, data.gfx_fd);
> igt_require(data.display.is_atomic);
>
> + /* Check if at least one active display connected */
> + igt_display_require_output(&data.display);
> +
> /* Get active pipes. */
> for_each_crtc(&data.display, crtc)
> active_crtcs[last_crtc_index++] = crtc->crtc_index;
next prev parent reply other threads:[~2026-03-25 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:59 [PATCH i-g-t] tests/kms_plane_alpha_blend: Print reason for test skips Sumit Kishore
2026-03-25 10:29 ` Sharma, Swati2 [this message]
2026-03-25 12:07 ` ✓ i915.CI.BAT: success for " Patchwork
2026-03-25 18:03 ` ✗ i915.CI.Full: failure " Patchwork
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=4f64f6c8-d3b0-4de1-8db7-16a37dbc6267@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=sumit.kishore@intel.com \
/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