public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Nidhi Gupta <nidhi1.gupta@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Nidhi Gupta <nidhi1.gupta@intel.com>
Subject: [igt-dev] [PATCH v4 7/7] tests/i915/kms_frontbuffer_tracking: Reduce the execution time on simulation
Date: Thu,  2 Feb 2023 10:45:09 +0530	[thread overview]
Message-ID: <20230202051509.28983-8-nidhi1.gupta@intel.com> (raw)
In-Reply-To: <20230202051509.28983-1-nidhi1.gupta@intel.com>

With IGT_DRAW_RENDER draw method test is taking lot of time to
complete causing timeout in simulation, to avoid the time out
skipping IGT_DRAW_METHOD only for simulation

Reviewed-by: Karthik B S <karthik.b.s@intel.com>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
---
 tests/i915/kms_frontbuffer_tracking.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tests/i915/kms_frontbuffer_tracking.c b/tests/i915/kms_frontbuffer_tracking.c
index 5b47999e..1d05a916 100644
--- a/tests/i915/kms_frontbuffer_tracking.c
+++ b/tests/i915/kms_frontbuffer_tracking.c
@@ -3159,6 +3159,9 @@ static void basic_subtest(const struct test_mode *t)
 	fb1 = params->primary.fb;
 
 	for (r = 0, method = 0; method < IGT_DRAW_METHOD_COUNT; method++) {
+		if (igt_run_in_simulation() && method == IGT_DRAW_RENDER)
+			continue;
+
 		if (method == IGT_DRAW_MMAP_GTT &&
 		    !gem_has_mappable_ggtt(drm.fd))
 			continue;
-- 
2.39.0

  parent reply	other threads:[~2023-02-02  5:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02  5:15 [igt-dev] [PATCH v4 0/7] Limit the execution to few pipes/planes Nidhi Gupta
2023-02-02  5:15 ` [igt-dev] [PATCH v4 1/7] tests/i915/kms_draw_crc: Ignore RGB565 & XRGB2101010 formats on simulation Nidhi Gupta
2023-02-02  5:15 ` [igt-dev] [PATCH v4 2/7] tests/kms_async_flips: Limit the execution to single pipe Nidhi Gupta
2023-02-02  5:15 ` [igt-dev] [PATCH v4 3/7] tests/kms_pipe_crc_basic: Limit the execution to two pipes Nidhi Gupta
2023-02-02 10:33   ` Modem, Bhanuprakash
2023-02-03  2:15   ` [igt-dev] [PATCH v5 " Nidhi Gupta
2023-02-03  5:49     ` [igt-dev] [i-g-t V3 " Bhanuprakash Modem
2023-02-02  5:15 ` [igt-dev] [PATCH v4 4/7] tests/kms_plane_alpha_blend: Limit the execution to single pipe & two planes Nidhi Gupta
2023-02-02  6:01   ` [igt-dev] [PATCH v5 " Nidhi Gupta
2023-02-02  7:00     ` Nidhi Gupta
2023-02-02 15:00       ` Kamil Konieczny
2023-02-02  5:15 ` [igt-dev] [PATCH v4 5/7] tests/kms_plane_cursor: Limit the execution to two pipes Nidhi Gupta
2023-02-02  5:15 ` [igt-dev] [PATCH v4 6/7] tests/kms_plane_scaling: Limit the execution to two pipes/planes Nidhi Gupta
2023-02-02  5:15 ` Nidhi Gupta [this message]
2023-02-02  5:51 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev2) Patchwork
2023-02-02  6:00 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Limit the execution to few pipes/planes (rev3) Patchwork
2023-02-02  6:00 ` [igt-dev] ✗ Fi.CI.BAT: failure for Limit the execution to few pipes/planes (rev2) Patchwork
2023-02-02  7:25 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev4) Patchwork
2023-02-02  7:26 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2023-02-02 15:45 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2023-02-03  2:40 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-03  7:16 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev6) Patchwork
2023-02-03 12:40 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-03 13:08 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev6) Patchwork
2023-02-03 17:48 ` [igt-dev] ✓ Fi.CI.IGT: success for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-04  0:12 ` [igt-dev] ✓ Fi.CI.IGT: success for Limit the execution to few pipes/planes (rev6) 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=20230202051509.28983-8-nidhi1.gupta@intel.com \
    --to=nidhi1.gupta@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox