From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Sowmiya S <sowmiya.s@intel.com>
Cc: igt-dev@lists.freedesktop.org, karthik.b.s@intel.com,
swati2.sharma@intel.com
Subject: Re: [PATCH i-g-t v1] tests/intel/kms_frontbuffer_tracking: Improve skip message
Date: Thu, 2 Apr 2026 13:16:29 +0300 [thread overview]
Message-ID: <ac5B_Qg-DRA5Q9P8@intel.com> (raw)
In-Reply-To: <20260402043702.914845-1-sowmiya.s@intel.com>
On Thu, Apr 02, 2026 at 10:07:02AM +0530, Sowmiya S wrote:
> Replace vague or negative skip messages with standardized,
> explicit descriptions that clearly state why a test is
> being skipped.
>
> Signed-off-by: Sowmiya S <sowmiya.s@intel.com>
> ---
> tests/intel/kms_frontbuffer_tracking.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tests/intel/kms_frontbuffer_tracking.c b/tests/intel/kms_frontbuffer_tracking.c
> index c16f63199..6a7017256 100644
> --- a/tests/intel/kms_frontbuffer_tracking.c
> +++ b/tests/intel/kms_frontbuffer_tracking.c
> @@ -2548,20 +2548,20 @@ 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,
> - "Can't test FBC with this chipset\n");
> + "feature not supported (feature: fbc)\n");
>
> if (t->feature & FEATURE_PSR) {
> igt_require_f(psr.can_test,
> - "Can't test PSR with the current outputs\n");
> + "feature not supported (feature: psr)\n");
> }
>
> if (t->feature & FEATURE_DRRS)
> igt_require_f(drrs.can_test,
> - "Can't test DRRS with the current outputs\n");
> + "feature not supported (feature: drrs)\n");
>
> /*
> * In kernel, When PSR is enabled, DRRS will be disabled. So If a test
> @@ -2569,7 +2569,7 @@ static void check_test_requirements(const struct test_mode *t)
> */
> igt_require_f(!((t->feature & FEATURE_PSR) &&
> (t->feature & FEATURE_DRRS)),
> - "Can't test PSR and DRRS together\n");
> + "incompatible features (feature: psr & drrs)\n");
This doesn't look like an improvement to me. The old one clearly
says what happened, this new one form looks like something meant
to confuses humans and be parsed by some machine.
>
> if (opt.only_pipes != PIPE_COUNT)
> igt_require(t->pipes == opt.only_pipes);
> --
> 2.43.0
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-04-02 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 4:37 [PATCH i-g-t v1] tests/intel/kms_frontbuffer_tracking: Improve skip message Sowmiya S
2026-04-02 5:08 ` ✓ i915.CI.BAT: success for " Patchwork
2026-04-02 5:24 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-02 8:58 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-02 10:16 ` Ville Syrjälä [this message]
2026-04-06 10:18 ` [PATCH i-g-t v1] " S, Sowmiya
2026-04-02 21:44 ` ✗ i915.CI.Full: failure for " 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=ac5B_Qg-DRA5Q9P8@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=sowmiya.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