All of lore.kernel.org
 help / color / mirror / Atom feed
From: krishnaiah.bommu@intel.com
To: igt-dev@lists.freedesktop.org
Cc: Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
	Konieczny Kamil <kamil.konieczny@intel.com>
Subject: [igt-dev] [PATCH] i915/gem_eio: increasing the timeout for forced reset completion
Date: Thu, 14 Apr 2022 15:53:04 +0530	[thread overview]
Message-ID: <20220414102304.1745-1-krishnaiah.bommu@intel.com> (raw)

From: Bommu Krishnaiah <krishnaiah.bommu@intel.com>

GUC log capture is taking more time on few platforms, so increasing the timeout

Signed-off-by: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
Cc: Konieczny Kamil <kamil.konieczny@intel.com>
Cc: John Harrison <john.c.harrison@intel.com>
Cc: Andi Shyti <andi.shyti@intel.com>
---
 tests/i915/gem_eio.c | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/tests/i915/gem_eio.c b/tests/i915/gem_eio.c
index d9689534d5a..94c3bc04644 100644
--- a/tests/i915/gem_eio.c
+++ b/tests/i915/gem_eio.c
@@ -72,8 +72,11 @@ static void trigger_reset(int fd)
 	igt_kmsg(KMSG_DEBUG "Forcing GPU reset\n");
 	igt_force_gpu_reset(fd);
 
-	/* The forced reset should be immediate */
-	igt_assert_lte(igt_seconds_elapsed(&ts), 2);
+	/* The forced reset should be immediate, even though
+	 * GUC log capture is taking more time on few platforms,
+	 * so Increasing the timeout
+	 */
+	igt_assert_lte(igt_seconds_elapsed(&ts), 10);
 
 	/* And just check the gpu is indeed running again */
 	igt_kmsg(KMSG_DEBUG "Checking that the GPU recovered\n");
-- 
2.25.1

             reply	other threads:[~2022-04-14 10:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 10:23 krishnaiah.bommu [this message]
2022-04-14 11:38 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_eio: increasing the timeout for forced reset completion Patchwork
2022-04-14 13:01 ` [igt-dev] [PATCH] " Kamil Konieczny
2022-04-14 13:38 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2022-04-18  5:04 [igt-dev] [PATCH] " krishnaiah.bommu
2022-04-18  5:29 ` Dixit, Ashutosh
2022-04-20  9:52 ` Kamil Konieczny

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=20220414102304.1745-1-krishnaiah.bommu@intel.com \
    --to=krishnaiah.bommu@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@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.