From: sumit kishore <sumit.kishore@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: kunal1.joshi@intel.com, sumit kishore <sumit.kishore@intel.com>
Subject: [PATCH i-g-t v1] tests/kms_plane_alpha_blend : print reason for test skips
Date: Tue, 3 Mar 2026 18:53:13 +0530 [thread overview]
Message-ID: <20260303132313.225994-1-sumit.kishore@intel.com> (raw)
Print debug message when tests are skipping on headless display systems
Signed-off-by: sumit kishore <sumit.kishore@intel.com>
---
tests/kms_plane_alpha_blend.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/tests/kms_plane_alpha_blend.c b/tests/kms_plane_alpha_blend.c
index 41a3b71c3..82d8eac62 100644
--- a/tests/kms_plane_alpha_blend.c
+++ b/tests/kms_plane_alpha_blend.c
@@ -753,9 +753,11 @@ const char *help_str =
int igt_main_args("e", NULL, help_str, opt_handler, NULL)
{
data_t data = {};
+ bool active_display = false;
igt_fixture() {
igt_crtc_t *crtc;
+ igt_output_t *output;
last_pipe = 0;
@@ -764,6 +766,13 @@ 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 */
+ for_each_connected_output(&data.display, output) {
+ active_display = true;
+ break;
+ }
+ igt_require_f(active_display, "No active display connected, skipping test\n");
+
/* Get active pipes. */
for_each_crtc(&data.display, crtc)
active_pipes[last_pipe++] = crtc->pipe;
--
2.43.0
next reply other threads:[~2026-03-03 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 13:23 sumit kishore [this message]
2026-03-04 2:39 ` ✓ Xe.CI.BAT: success for tests/kms_plane_alpha_blend : print reason for test skips Patchwork
2026-03-04 3:03 ` ✓ i915.CI.BAT: " Patchwork
2026-03-04 14:14 ` [PATCH i-g-t v1] " Kamil Konieczny
2026-03-04 22:37 ` ✗ Xe.CI.FULL: failure for " Patchwork
2026-03-05 5:33 ` [PATCH i-g-t v1] " Karthik B S
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=20260303132313.225994-1-sumit.kishore@intel.com \
--to=sumit.kishore@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kunal1.joshi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.