From: Sowmiya S <sowmiya.s@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: karthik.b.s@intel.com, swati2.sharma@intel.com,
Sowmiya S <sowmiya.s@intel.com>
Subject: [PATCH i-g-t v3] tests/intel/kms_frontbuffer_tracking: Improve skip message
Date: Thu, 9 Apr 2026 12:09:24 +0530 [thread overview]
Message-ID: <20260409063924.1048289-1-sowmiya.s@intel.com> (raw)
Update the dual‑pipe skip message to explicitly
report that no valid secondary output is available.
This avoids ambiguity when reading test logs.
v2: Address review comments (Ville)
v3: Provide clear commit message (Swati)
Signed-off-by: Sowmiya S <sowmiya.s@intel.com>
Reviewed-by: Swati Sharma <swati2.sharma@intel.com>
---
tests/intel/kms_frontbuffer_tracking.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/intel/kms_frontbuffer_tracking.c b/tests/intel/kms_frontbuffer_tracking.c
index c16f63199..8b73e8505 100644
--- a/tests/intel/kms_frontbuffer_tracking.c
+++ b/tests/intel/kms_frontbuffer_tracking.c
@@ -2548,7 +2548,7 @@ static void check_test_requirements(const struct test_mode *t)
{
if (t->pipes == PIPE_DUAL)
igt_require_f(scnd_mode_params.output,
- "Can't test dual pipes with the current outputs\n");
+ "no valid secondary output available for dual-pipe tests\n");
if (t->feature & FEATURE_FBC)
igt_require_f(fbc.can_test,
--
2.43.0
next reply other threads:[~2026-04-09 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 6:39 Sowmiya S [this message]
2026-04-10 1:14 ` ✓ Xe.CI.BAT: success for tests/intel/kms_frontbuffer_tracking: Improve skip message (rev3) Patchwork
2026-04-10 1:18 ` ✓ i915.CI.BAT: " Patchwork
2026-04-10 4:05 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-10 18:48 ` ✗ 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=20260409063924.1048289-1-sowmiya.s@intel.com \
--to=sowmiya.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=swati2.sharma@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