Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshi, Kunal1" <kunal1.joshi@intel.com>
To: Naladala Ramanaidu <ramanaidu.naladala@intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [i-g-t, v3, 2/3] tests/kms_plane_scaling: Improve error handling in kms_plane_scaling tests
Date: Fri, 27 Sep 2024 23:10:51 +0530	[thread overview]
Message-ID: <c075de84-dd29-4a11-9c25-6df325f40028@intel.com> (raw)
In-Reply-To: <20240926181150.2148704-3-ramanaidu.naladala@intel.com>


On 26-09-2024 23:41, Naladala Ramanaidu wrote:
> Refactor error handling in test_planes_scaling_combo to use break
> statements instead of immediate returns. This ensures cleanup_fbs
> is always called before exiting the loop. Additionally, adjust log
> message formatting in igt_main_args for consistency.
>
> Signed-off-by: Naladala Ramanaidu <ramanaidu.naladala@intel.com>
Reviewed-by: Kunal Joshi <kunal1.joshi@intel.com>
> ---
>   tests/kms_plane_scaling.c | 10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> index 96ceedee2..a55720ed9 100644
> --- a/tests/kms_plane_scaling.c
> +++ b/tests/kms_plane_scaling.c
> @@ -998,12 +998,12 @@ test_planes_scaling_combo(data_t *d, double sf_plane1,
>   							  pipe, output, p1, p2,
>   							  &d->fb[1], &d->fb[2],
>   							  test_type);
> -			if (ret != 0) {
> -				cleanup_fbs(d);
> -				return ret;
> -			}
> +			if (ret != 0)
> +				break;
>   		}
>   		cleanup_fbs(d);
> +		if (ret == 0)
> +			break;
>   	}
>   	return ret;
>   }
> @@ -1543,7 +1543,7 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>   								scaler_with_2_planes_tests[index].test_type);
>   							if (ret == 0)
>   								break;
> -							igt_info("Required Scaling operation not supported on %s trying on next output\n",
> +							igt_info("Required scaling operation not supported on %s trying on next output\n",
>   								 igt_output_name(output));
>   						}
>   						igt_skip_on_f(ret == -ERANGE || ret == -EINVAL,

  reply	other threads:[~2024-09-27 17:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 18:11 [PATCH i-g-t v3 0/3] tests/kms_plane_scaling: Cdclk exceeds max Cdclk issue fix Naladala Ramanaidu
2024-09-26 18:11 ` [PATCH i-g-t v3 1/3] tests/kms_plane_scaling: Add mode override in scaling test Naladala Ramanaidu
2024-09-26 18:11 ` [PATCH i-g-t v3 2/3] tests/kms_plane_scaling: Improve error handling in kms_plane_scaling tests Naladala Ramanaidu
2024-09-27 17:40   ` Joshi, Kunal1 [this message]
2024-09-26 18:11 ` [PATCH i-g-t v3 3/3] HAX patch do not merge Naladala Ramanaidu
2024-09-26 19:09 ` ✗ Fi.CI.BAT: failure for tests/kms_plane_scaling: Cdclk exceeds max Cdclk issue fix (rev3) Patchwork
2024-09-26 19:21 ` ✗ CI.xeBAT: " Patchwork
2024-09-27 19:56 ` ✗ CI.xeFULL: " Patchwork
2024-10-01 13:35 ` ✗ Fi.CI.BAT: " Patchwork
2024-10-07 19:01 ` ✗ GitLab.Pipeline: warning for tests/kms_plane_scaling: Cdclk exceeds max Cdclk issue fix (rev4) Patchwork
2024-10-07 19:26 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-07 19:34 ` ✗ CI.xeBAT: " Patchwork
2024-10-08  8:12 ` ✗ CI.xeFULL: " Patchwork
2024-10-15  9:44 ` ✗ Fi.CI.BUILD: failure for tests/kms_plane_scaling: Cdclk exceeds max Cdclk issue fix (rev5) 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=c075de84-dd29-4a11-9c25-6df325f40028@intel.com \
    --to=kunal1.joshi@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ramanaidu.naladala@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