Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] tests/kms_flip: Restrict the hang tests execution to first and last pipe combinations
Date: Tue, 18 Jul 2023 16:30:06 +0530	[thread overview]
Message-ID: <20230718110006.28283-1-jeevan.b@intel.com> (raw)

restrict the hang tests execution to single pipe combinations still
causing timed-out so limiting the combination to first and last pipe.

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

diff --git a/tests/kms_flip.c b/tests/kms_flip.c
index ef2234f74..ee4e8a43d 100755
--- a/tests/kms_flip.c
+++ b/tests/kms_flip.c
@@ -1729,10 +1729,14 @@ static void run_pair(int duration, int flags)
 					crtc_idxs[0] = n;
 					crtc_idxs[1] = m;
 
-					/* Limit the execution to PIPE_A combination for hang tests */
+					/* Limit the execution to 2 CRTCs
+					 * (first and last combination) for hang tests */
 					if ((flags & TEST_HANG) && !all_pipes &&
 					    (n != 0 && n != resources->count_crtcs))
 						continue;
+					if ((flags & TEST_HANG) && !all_pipes &&
+					    m != resources->count_crtcs - 1)
+						continue;
 
 					run_test_on_crtc_set(&o, crtc_idxs,
 							     RUN_PAIR,
-- 
2.41.0

             reply	other threads:[~2023-07-18 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 11:00 Jeevan B [this message]
2023-07-18 13:33 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_flip: Restrict the hang tests execution to first and last pipe combinations Patchwork
2023-07-18 14:05 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-07-18 17:55 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-26 15:02 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-07-27  5:21   ` B, Jeevan

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=20230718110006.28283-1-jeevan.b@intel.com \
    --to=jeevan.b@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