All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: swati2.sharma@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: [PATCH i-g-t] tests/kms_display_modes: reduce exec. time for sim env
Date: Thu,  4 Sep 2025 09:13:12 +0530	[thread overview]
Message-ID: <20250904034312.1264838-1-jeevan.b@intel.com> (raw)

For simulation environment, we can reduce execution time
by running test only with one combination.

v2: Remove redundant simulation check by using flag

Signed-off-by: Jeevan B <jeevan.b@intel.com>
---
 tests/kms_display_modes.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tests/kms_display_modes.c b/tests/kms_display_modes.c
index c93195b3c..e95e334d2 100644
--- a/tests/kms_display_modes.c
+++ b/tests/kms_display_modes.c
@@ -180,6 +180,7 @@ static void run_extendedmode_basic(data_t *data,
 
 static void run_extendedmode_test(data_t *data) {
 	enum pipe pipe1, pipe2;
+	bool sim_flag = igt_run_in_simulation();
 	igt_output_t *output1, *output2;
 	igt_display_t *display = &data->display;
 
@@ -218,9 +219,11 @@ static void run_extendedmode_test(data_t *data) {
 			 * For simulation env, no need to run
 			 * test with each valid output on pipe.
 			 */
-			if (igt_run_in_simulation())
+			if (sim_flag)
 				break;
 		}
+		if (sim_flag)
+			break;
 	}
 }
 
-- 
2.43.0


             reply	other threads:[~2025-09-04  3:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04  3:43 Jeevan B [this message]
2025-09-04  4:29 ` ✓ Xe.CI.BAT: success for tests/kms_display_modes: reduce exec. time for sim env (rev2) Patchwork
2025-09-04  4:40 ` ✓ i915.CI.BAT: " Patchwork
2025-09-04 13:24 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-05  5:20 ` ✗ i915.CI.Full: " Patchwork
2025-09-17  8:08 ` [PATCH i-g-t] tests/kms_display_modes: reduce exec. time for sim env Sharma, Swati2
  -- strict thread matches above, loose matches on Subject: below --
2025-09-01  6:36 Jeevan B
2025-09-03  7:43 ` Sharma, Swati2

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=20250904034312.1264838-1-jeevan.b@intel.com \
    --to=jeevan.b@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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 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.