* [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes
@ 2023-02-28 4:24 Nidhi Gupta
2023-02-28 4:46 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_color: Limit the execution to two pipes (rev2) Patchwork
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Nidhi Gupta @ 2023-02-28 4:24 UTC (permalink / raw)
To: igt-dev; +Cc: Nidhi Gupta
As the test execution is taking more time on simulation, limit the
execution to two (first & last) pipes. This optimization is for
simulation and hardware.
This patch will also provide an option (command line flag '-e') to
execute on all pipes.
Example: ./kms_color -e --run-subtest ctm-0-50
v2: Restrict the execution only on 2 pipes for
real hardware aswell (Ankit)
v3: Restrict the execution only on 2 pipes for
all subtests (Bhanu)
Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
---
tests/kms_color.c | 43 ++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 42 insertions(+), 1 deletion(-)
diff --git a/tests/kms_color.c b/tests/kms_color.c
index 45570083..85d9100f 100644
--- a/tests/kms_color.c
+++ b/tests/kms_color.c
@@ -26,6 +26,10 @@
IGT_TEST_DESCRIPTION("Test Color Features at Pipe level");
+static bool extended;
+static enum pipe active_pipes[IGT_MAX_PIPES];
+static uint32_t last_pipe;
+
static bool test_pipe_degamma(data_t *data,
igt_plane_t *primary)
{
@@ -878,6 +882,16 @@ run_deep_color_tests_for_pipe(data_t *data, enum pipe p)
test_cleanup(data);
}
+static bool execution_constraint(enum pipe pipe)
+{
+ if (!extended &&
+ pipe != active_pipes[0] &&
+ pipe != active_pipes[last_pipe])
+ return true;
+
+ return false;
+}
+
static void
run_invalid_tests_for_pipe(data_t *data)
{
@@ -1022,6 +1036,9 @@ run_tests_for_pipe(data_t *data)
igt_describe_f("%s", ctm_tests[i].desc);
igt_subtest_with_dynamic_f("%s", ctm_tests[i].name) {
for_each_pipe(&data->display, pipe) {
+ if (execution_constraint(pipe))
+ continue;
+
run_ctm_tests_for_pipe(data, pipe,
ctm_tests[i].colors,
ctm_tests[i].ctm,
@@ -1041,9 +1058,28 @@ run_tests_for_pipe(data_t *data)
}
}
-igt_main
+static int opt_handler(int opt, int opt_index, void *_data)
+{
+ switch (opt) {
+ case 'e':
+ extended = true;
+ break;
+ default:
+ return IGT_OPT_HANDLER_ERROR;
+ }
+
+ return IGT_OPT_HANDLER_SUCCESS;
+}
+
+const char *help_str =
+ " -e \tExtended tests.\n";
+
+igt_main_args("e", NULL, help_str, opt_handler, NULL)
{
data_t data = {};
+ enum pipe pipe;
+
+ last_pipe = 0;
igt_fixture {
data.drm_fd = drm_open_driver_master(DRIVER_ANY);
@@ -1052,6 +1088,11 @@ igt_main
kmstest_set_vt_graphics_mode();
igt_display_require(&data.display, data.drm_fd);
+
+ /* Get active pipes. */
+ for_each_pipe(&data.display, pipe)
+ active_pipes[last_pipe++] = pipe;
+ last_pipe--;
}
igt_subtest_group
--
2.39.0
^ permalink raw reply related [flat|nested] 5+ messages in thread* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_color: Limit the execution to two pipes (rev2)
2023-02-28 4:24 [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes Nidhi Gupta
@ 2023-02-28 4:46 ` Patchwork
2023-02-28 4:56 ` [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes Modem, Bhanuprakash
2023-02-28 7:09 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_color: Limit the execution to two pipes (rev2) Patchwork
2 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2023-02-28 4:46 UTC (permalink / raw)
To: Nidhi Gupta; +Cc: igt-dev
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
== Series Details ==
Series: tests/kms_color: Limit the execution to two pipes (rev2)
URL : https://patchwork.freedesktop.org/series/114389/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12789 -> IGTPW_8535
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/index.html
Participating hosts (38 -> 37)
------------------------------
Missing (1): fi-snb-2520m
Changes
-------
No changes found
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_7174 -> IGTPW_8535
CI-20190529: 20190529
CI_DRM_12789: 8589fd9227ca62484e8599cbd62216230c2c9a64 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_8535: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/index.html
IGT_7174: 55642b7805d6fc5b987b396c2bbfa46db654db4f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Testlist changes
----------------
-igt@kms_plane@invalid-pixel-format-settings
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/index.html
[-- Attachment #2: Type: text/html, Size: 1697 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes
2023-02-28 4:24 [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes Nidhi Gupta
2023-02-28 4:46 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_color: Limit the execution to two pipes (rev2) Patchwork
@ 2023-02-28 4:56 ` Modem, Bhanuprakash
2023-02-28 7:09 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_color: Limit the execution to two pipes (rev2) Patchwork
2 siblings, 0 replies; 5+ messages in thread
From: Modem, Bhanuprakash @ 2023-02-28 4:56 UTC (permalink / raw)
To: Nidhi Gupta, igt-dev
Hi Nidhi,
On Tue-28-02-2023 09:54 am, Nidhi Gupta wrote:
> As the test execution is taking more time on simulation, limit the
> execution to two (first & last) pipes. This optimization is for
> simulation and hardware.
>
> This patch will also provide an option (command line flag '-e') to
> execute on all pipes.
>
> Example: ./kms_color -e --run-subtest ctm-0-50
>
> v2: Restrict the execution only on 2 pipes for
> real hardware aswell (Ankit)
> v3: Restrict the execution only on 2 pipes for
> all subtests (Bhanu)
Still, this change is not present in this patch.
- Bhanu
>
> Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
> ---
> tests/kms_color.c | 43 ++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 42 insertions(+), 1 deletion(-)
>
> diff --git a/tests/kms_color.c b/tests/kms_color.c
> index 45570083..85d9100f 100644
> --- a/tests/kms_color.c
> +++ b/tests/kms_color.c
> @@ -26,6 +26,10 @@
>
> IGT_TEST_DESCRIPTION("Test Color Features at Pipe level");
>
> +static bool extended;
> +static enum pipe active_pipes[IGT_MAX_PIPES];
> +static uint32_t last_pipe;
> +
> static bool test_pipe_degamma(data_t *data,
> igt_plane_t *primary)
> {
> @@ -878,6 +882,16 @@ run_deep_color_tests_for_pipe(data_t *data, enum pipe p)
> test_cleanup(data);
> }
>
> +static bool execution_constraint(enum pipe pipe)
> +{
> + if (!extended &&
> + pipe != active_pipes[0] &&
> + pipe != active_pipes[last_pipe])
> + return true;
> +
> + return false;
> +}
> +
> static void
> run_invalid_tests_for_pipe(data_t *data)
> {
> @@ -1022,6 +1036,9 @@ run_tests_for_pipe(data_t *data)
> igt_describe_f("%s", ctm_tests[i].desc);
> igt_subtest_with_dynamic_f("%s", ctm_tests[i].name) {
> for_each_pipe(&data->display, pipe) {
> + if (execution_constraint(pipe))
> + continue;
> +
> run_ctm_tests_for_pipe(data, pipe,
> ctm_tests[i].colors,
> ctm_tests[i].ctm,
> @@ -1041,9 +1058,28 @@ run_tests_for_pipe(data_t *data)
> }
> }
>
> -igt_main
> +static int opt_handler(int opt, int opt_index, void *_data)
> +{
> + switch (opt) {
> + case 'e':
> + extended = true;
> + break;
> + default:
> + return IGT_OPT_HANDLER_ERROR;
> + }
> +
> + return IGT_OPT_HANDLER_SUCCESS;
> +}
> +
> +const char *help_str =
> + " -e \tExtended tests.\n";
> +
> +igt_main_args("e", NULL, help_str, opt_handler, NULL)
> {
> data_t data = {};
> + enum pipe pipe;
> +
> + last_pipe = 0;
>
> igt_fixture {
> data.drm_fd = drm_open_driver_master(DRIVER_ANY);
> @@ -1052,6 +1088,11 @@ igt_main
> kmstest_set_vt_graphics_mode();
>
> igt_display_require(&data.display, data.drm_fd);
> +
> + /* Get active pipes. */
> + for_each_pipe(&data.display, pipe)
> + active_pipes[last_pipe++] = pipe;
> + last_pipe--;
> }
>
> igt_subtest_group
^ permalink raw reply [flat|nested] 5+ messages in thread* [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_color: Limit the execution to two pipes (rev2)
2023-02-28 4:24 [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes Nidhi Gupta
2023-02-28 4:46 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_color: Limit the execution to two pipes (rev2) Patchwork
2023-02-28 4:56 ` [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes Modem, Bhanuprakash
@ 2023-02-28 7:09 ` Patchwork
2 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2023-02-28 7:09 UTC (permalink / raw)
To: Nidhi Gupta; +Cc: igt-dev
[-- Attachment #1: Type: text/plain, Size: 9520 bytes --]
== Series Details ==
Series: tests/kms_color: Limit the execution to two pipes (rev2)
URL : https://patchwork.freedesktop.org/series/114389/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12789_full -> IGTPW_8535_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_8535_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_8535_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/index.html
Participating hosts (8 -> 8)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_8535_full:
### IGT changes ###
#### Possible regressions ####
* igt@prime_vgem@fence-wait@rcs0:
- shard-glk: NOTRUN -> [ABORT][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-glk3/igt@prime_vgem@fence-wait@rcs0.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@prime_vgem@fence-wait@rcs0:
- {shard-dg1}: NOTRUN -> [ABORT][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-dg1-14/igt@prime_vgem@fence-wait@rcs0.html
Known issues
------------
Here are the changes found in IGTPW_8535_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_eio@in-flight-10ms:
- shard-apl: NOTRUN -> [ABORT][3] ([i915#8233]) +4 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-apl6/igt@gem_eio@in-flight-10ms.html
- shard-glk: NOTRUN -> [ABORT][4] ([i915#8233]) +3 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-glk7/igt@gem_eio@in-flight-10ms.html
* igt@gem_huc_copy@huc-copy:
- shard-apl: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#2190])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-apl6/igt@gem_huc_copy@huc-copy.html
- shard-glk: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-glk7/igt@gem_huc_copy@huc-copy.html
* igt@gem_lmem_swapping@heavy-verify-random-ccs:
- shard-apl: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#4613])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-apl6/igt@gem_lmem_swapping@heavy-verify-random-ccs.html
* igt@gem_wait@write-busy@bcs0:
- shard-glk: NOTRUN -> [DMESG-WARN][8] ([i915#8233]) +3 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-glk7/igt@gem_wait@write-busy@bcs0.html
* igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#3886]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-glk7/igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#3886]) +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-apl6/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_content_protection@srm@pipe-a-dp-1:
- shard-apl: NOTRUN -> [TIMEOUT][11] ([i915#7173])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-apl6/igt@kms_content_protection@srm@pipe-a-dp-1.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-big-fb:
- shard-apl: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#658])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-apl6/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-big-fb.html
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-glk: NOTRUN -> [SKIP][13] ([fdo#109271]) +20 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-glk3/igt@kms_psr@psr2_sprite_mmap_gtt.html
* igt@kms_psr@psr2_sprite_plane_onoff:
- shard-apl: NOTRUN -> [SKIP][14] ([fdo#109271]) +45 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-apl6/igt@kms_psr@psr2_sprite_plane_onoff.html
* igt@kms_writeback@writeback-check-output:
- shard-glk: NOTRUN -> [SKIP][15] ([fdo#109271] / [i915#2437])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/shard-glk7/igt@kms_writeback@writeback-check-output.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109302]: https://bugs.freedesktop.org/show_bug.cgi?id=109302
[fdo#109307]: https://bugs.freedesktop.org/show_bug.cgi?id=109307
[fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#4565]: https://gitlab.freedesktop.org/drm/intel/issues/4565
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4771]: https://gitlab.freedesktop.org/drm/intel/issues/4771
[i915#4818]: https://gitlab.freedesktop.org/drm/intel/issues/4818
[i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#4880]: https://gitlab.freedesktop.org/drm/intel/issues/4880
[i915#4881]: https://gitlab.freedesktop.org/drm/intel/issues/4881
[i915#4958]: https://gitlab.freedesktop.org/drm/intel/issues/4958
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289
[i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325
[i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#7173]: https://gitlab.freedesktop.org/drm/intel/issues/7173
[i915#7711]: https://gitlab.freedesktop.org/drm/intel/issues/7711
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#8233]: https://gitlab.freedesktop.org/drm/intel/issues/8233
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_7174 -> IGTPW_8535
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_12789: 8589fd9227ca62484e8599cbd62216230c2c9a64 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_8535: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/index.html
IGT_7174: 55642b7805d6fc5b987b396c2bbfa46db654db4f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8535/index.html
[-- Attachment #2: Type: text/html, Size: 7849 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes
@ 2023-02-28 5:12 Nidhi Gupta
0 siblings, 0 replies; 5+ messages in thread
From: Nidhi Gupta @ 2023-02-28 5:12 UTC (permalink / raw)
To: igt-dev; +Cc: Nidhi Gupta
As the test execution is taking more time on simulation, limit the
execution to two (first & last) pipes. This optimization is for
simulation and hardware.
This patch will also provide an option (command line flag '-e') to
execute on all pipes.
Example: ./kms_color -e --run-subtest ctm-0-50
v2: Restrict the execution only on 2 pipes for
real hardware aswell (Ankit)
v3: Restrict the execution only on 2 pipes for
all subtests (Bhanu)
Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
---
tests/kms_color.c | 52 ++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 51 insertions(+), 1 deletion(-)
diff --git a/tests/kms_color.c b/tests/kms_color.c
index 45570083..54580315 100644
--- a/tests/kms_color.c
+++ b/tests/kms_color.c
@@ -26,6 +26,10 @@
IGT_TEST_DESCRIPTION("Test Color Features at Pipe level");
+static bool extended;
+static enum pipe active_pipes[IGT_MAX_PIPES];
+static uint32_t last_pipe;
+
static bool test_pipe_degamma(data_t *data,
igt_plane_t *primary)
{
@@ -878,6 +882,16 @@ run_deep_color_tests_for_pipe(data_t *data, enum pipe p)
test_cleanup(data);
}
+static bool execution_constraint(enum pipe pipe)
+{
+ if (!extended &&
+ pipe != active_pipes[0] &&
+ pipe != active_pipes[last_pipe])
+ return true;
+
+ return false;
+}
+
static void
run_invalid_tests_for_pipe(data_t *data)
{
@@ -902,6 +916,9 @@ run_invalid_tests_for_pipe(data_t *data)
igt_describe_f("%s", tests[i].desc);
igt_subtest_with_dynamic_f("%s", tests[i].name) {
for_each_pipe(&data->display, pipe) {
+ if (execution_constraint(pipe))
+ continue;
+
prep_pipe(data, pipe);
igt_dynamic_f("pipe-%s", kmstest_pipe_name(pipe))
@@ -1012,6 +1029,9 @@ run_tests_for_pipe(data_t *data)
igt_describe_f("%s", gamma_degamma_tests[i].desc);
igt_subtest_with_dynamic_f("%s", gamma_degamma_tests[i].name) {
for_each_pipe(&data->display, pipe) {
+ if (execution_constraint(pipe))
+ continue;
+
run_gamma_degamma_tests_for_pipe(data, pipe,
gamma_degamma_tests[i].test_t);
}
@@ -1022,6 +1042,9 @@ run_tests_for_pipe(data_t *data)
igt_describe_f("%s", ctm_tests[i].desc);
igt_subtest_with_dynamic_f("%s", ctm_tests[i].name) {
for_each_pipe(&data->display, pipe) {
+ if (execution_constraint(pipe))
+ continue;
+
run_ctm_tests_for_pipe(data, pipe,
ctm_tests[i].colors,
ctm_tests[i].ctm,
@@ -1036,14 +1059,36 @@ run_tests_for_pipe(data_t *data)
igt_describe("Verify that deep color works correctly");
igt_subtest_with_dynamic("deep-color") {
for_each_pipe(&data->display, pipe) {
+ if (execution_constraint(pipe))
+ continue;
+
run_deep_color_tests_for_pipe(data, pipe);
}
}
}
-igt_main
+static int opt_handler(int opt, int opt_index, void *_data)
+{
+ switch (opt) {
+ case 'e':
+ extended = true;
+ break;
+ default:
+ return IGT_OPT_HANDLER_ERROR;
+ }
+
+ return IGT_OPT_HANDLER_SUCCESS;
+}
+
+const char *help_str =
+ " -e \tExtended tests.\n";
+
+igt_main_args("e", NULL, help_str, opt_handler, NULL)
{
data_t data = {};
+ enum pipe pipe;
+
+ last_pipe = 0;
igt_fixture {
data.drm_fd = drm_open_driver_master(DRIVER_ANY);
@@ -1052,6 +1097,11 @@ igt_main
kmstest_set_vt_graphics_mode();
igt_display_require(&data.display, data.drm_fd);
+
+ /* Get active pipes. */
+ for_each_pipe(&data.display, pipe)
+ active_pipes[last_pipe++] = pipe;
+ last_pipe--;
}
igt_subtest_group
--
2.39.0
^ permalink raw reply related [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-02-28 7:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-02-28 4:24 [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes Nidhi Gupta
2023-02-28 4:46 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_color: Limit the execution to two pipes (rev2) Patchwork
2023-02-28 4:56 ` [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes Modem, Bhanuprakash
2023-02-28 7:09 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_color: Limit the execution to two pipes (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-02-28 5:12 [igt-dev] [PATCH i-g-t v3] tests/kms_color: Limit the execution to two pipes Nidhi Gupta
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox