All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gupta, Nidhi1" <nidhi1.gupta@intel.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/kms : Added dynamic test cases
Date: Tue, 19 Apr 2022 07:33:40 +0000	[thread overview]
Message-ID: <12890197ce9340c89da5c3bb37d78a68@intel.com> (raw)
In-Reply-To: <631db0bd-e105-847b-5e85-99dfd42cf0a8@intel.com>



-----Original Message-----
From: Modem, Bhanuprakash <bhanuprakash.modem@intel.com> 
Sent: Monday, April 18, 2022 4:24 PM
To: Gupta, Nidhi1 <nidhi1.gupta@intel.com>; igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v2] tests/kms : Added dynamic test cases

On Mon-18-04-2022 01:23 pm, Nidhi Gupta wrote:
> Modified kms_sequence and kms_concurrent to include dynamic test 
> cases.
> 
> Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
> ---
>   tests/kms_concurrent.c |  6 ++++--
>   tests/kms_sequence.c   | 13 ++++++++++---
>   2 files changed, 14 insertions(+), 5 deletions(-)
> 
> diff --git a/tests/kms_concurrent.c b/tests/kms_concurrent.c index 
> dc1e36f2..5536a369 100644
> --- a/tests/kms_concurrent.c
> +++ b/tests/kms_concurrent.c
> @@ -339,9 +339,11 @@ run_tests_for_pipe(data_t *data, enum pipe pipe)
>   
>   	igt_describe("Test atomic mode setting concurrently with multiple planes and screen "
>   		     "resolution.");
> -	igt_subtest_f("pipe-%s", kmstest_pipe_name(pipe))
> +	igt_subtest_with_dynamic_f("pipe-%s", kmstest_pipe_name(pipe)) {
>   		for_each_valid_output_on_pipe(&data->display, pipe, output)
> -			run_test(data, pipe, output);
> +			igt_dynamic_f("%s", igt_output_name(output))
> +				run_test(data, pipe, output);

You need to remove for_each_valid_output_on_pipe() logic from run_test(), since we already doing here the same.
I already added this in IGT cleanup patch, to avoid the confusion I send a new series with 2 patches, one IGT cleanup and other dynamic tests

> +	}
>   }
>   
>   static int opt_handler(int option, int option_index, void *input) 
> diff --git a/tests/kms_sequence.c b/tests/kms_sequence.c index 
> 9c287480..aeabce23 100644
> --- a/tests/kms_sequence.c
> +++ b/tests/kms_sequence.c
> @@ -253,6 +253,7 @@ static void sequence_queue(data_t *data, int fd, int nchildren)
>   igt_main
>   {
>   	int fd;
> +	igt_output_t *output;
>   	data_t data;
>   	const struct {
>   		const char *name;
> @@ -278,6 +279,7 @@ igt_main
>   		fd = drm_open_driver_master(DRIVER_ANY);
>   		kmstest_set_vt_graphics_mode();
>   		igt_display_require(&data.display, fd);
> +		igt_display_require_output(&data.display);
>   	}
>   
>   	for (f = funcs; f->name; f++) {
> @@ -287,9 +289,14 @@ igt_main
>   
>   			igt_describe("This is a test of drmCrtcGetSequence and "
>   				     "drmCrtcQueueSequence");
> -			igt_subtest_f("%s-%s", f->name, m->name) {
> -				data.flags = m->flags;
> -				run_test(&data, fd, f->func);
> +			igt_subtest_with_dynamic_f("%s-%s", f->name, m->name) {
> +				for_each_connected_output(&data.display, output) {
> +					igt_dynamic_f("%s", igt_output_name(output)) {
> +						data.output = output;

We are no where using this "data.output".

Actually, run_test() is iterating for_each_pipe_with_valid_output() to get valid pipe/connector combination.

If you want to create dynamic subtests with pipe/connector config, you need to iterate for_each_pipe_with_valid_output() before calling
igt_dynamic() and remove the same logic from run_test().

- Bhanu

> +						data.flags = m->flags;
> +						run_test(&data, fd, f->func);
> +					}
> +				}
>   			}
>   		}
>   	}


      reply	other threads:[~2022-04-19  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18  7:53 [igt-dev] [PATCH i-g-t v2] tests/kms : Added dynamic test cases Nidhi Gupta
2022-04-18  8:36 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-04-18  9:48 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-04-18 10:53 ` [igt-dev] [PATCH i-g-t v2] " Modem, Bhanuprakash
2022-04-19  7:33   ` Gupta, Nidhi1 [this message]

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=12890197ce9340c89da5c3bb37d78a68@intel.com \
    --to=nidhi1.gupta@intel.com \
    --cc=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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.