Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: nidhi1.gupta@intel.com
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [RFC, i-g-t] Added Dynamic Subtest
Date: Tue, 1 Dec 2020 15:44:52 +0200	[thread overview]
Message-ID: <20201201134452.GB7444@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20201201023258.5351-1-nidhi1.gupta@intel.com>

On Tue, Dec 01, 2020 at 08:02:58AM +0530, nidhi1.gupta@intel.com wrote:
> From: Nidhi Gupta <nidhi1.gupta@intel.com>
> 
> In kms_plane_scaling have a subtest with 2 pipe it
> will execute it weather 2 pipes are available or not.
> Later it has to be analysed and discard it as valid skip.
> To save this time updated in test to first check the available
> outputs and then execute the test
> Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
> ---
>  tests/kms_plane_scaling.c | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> index 89b82416..95be07cc 100644
> --- a/tests/kms_plane_scaling.c
> +++ b/tests/kms_plane_scaling.c
> @@ -682,6 +682,7 @@ static data_t data;
>  igt_main_args("", long_opts, help_str, opt_handler, &data)
>  {
>  	enum pipe pipe;
> +	int count = 0;
>  
>  	igt_fixture {
>  		data.drm_fd = drm_open_driver_master(DRIVER_INTEL | DRIVER_AMDGPU);
> @@ -717,10 +718,17 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>  				igt_dynamic_f("pipe-%s-scaler-with-clipping-clamping", kmstest_pipe_name(pipe))
>  					test_scaler_with_clipping_clamping_scenario(&data, pipe, output);
>  		}
> -	}
>  
> -	igt_subtest_f("2x-scaler-multi-pipe")
> -		test_scaler_with_multi_pipe_plane(&data);
> +		igt_subtest_with_dynamic("scaler-multi-pipe") {
> +			for_each_pipe_with_single_output(&data.display, pipe, output) {
> +				++count;
> +			}
> +			if (count >= 2) {
> +				igt_dynamic_f("2x-scaler-multi-pipe")
> +					test_scaler_with_multi_pipe_plane(&data);
> +			}
> +		}
> +	}

NAK. This will make the test still skip on less than 2 outputs, but
the skip is now harder to filter. (The skip will be for
"scaler-multi-pipe" with the message "no dynamic subtests entered")

To save human time in cibuglog analysis, rather make the
less-than-required-outputs skip messages consistent so one filter can
cover them all.


-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2020-12-01 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01  2:32 [igt-dev] [RFC, i-g-t] Added Dynamic Subtest nidhi1.gupta
2020-12-01  3:16 ` [igt-dev] ✓ Fi.CI.BAT: success for Added dynamic Subtest (rev6) Patchwork
2020-12-01 13:44 ` Petri Latvala [this message]
2020-12-01 15:59 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2020-11-06  9:27 [igt-dev] [RFC, i-g-t] Added dynamic Subtest nidhi1.gupta
2020-11-06  9:34 ` Petri Latvala
2020-11-11  9:42   ` Karthik B S
2020-11-11 10:26     ` Petri Latvala

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=20201201134452.GB7444@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=nidhi1.gupta@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