public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tomasz Lis <tomasz.lis@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] tests/prime_busy: Increase timeout to mind pre-silicon.
Date: Wed, 29 May 2019 15:53:32 +0200	[thread overview]
Message-ID: <20190529135332.3099-1-tomasz.lis@intel.com> (raw)

From: "Lis, Tomasz" <tomasz.lis@intel.com>

On silicon, simple submission is finished much faster than in a second.
But for pre-silicon, it is not always the case. Six seconds should be
enough though.

Signed-off-by: Tomasz Lis <tomasz.lis@intel.com>
Cc: Mrzyglod Daniel T <daniel.t.mrzyglod@intel.com>
Cc: Michal Winiarski <michal.winiarski@intel.com>
Cc: Katarzyna Dec <katarzyna.dec@intel.com>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
---
 tests/prime_busy.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/prime_busy.c b/tests/prime_busy.c
index a82acbdb..8e0f3ca6 100644
--- a/tests/prime_busy.c
+++ b/tests/prime_busy.c
@@ -147,7 +147,7 @@ static void busy(int fd, unsigned ring, unsigned flags)
 	if ((flags & HANG) == 0) {
 		*bbe = MI_BATCH_BUFFER_END;
 		__sync_synchronize();
-		timeout = 1;
+		timeout = 6;
 	}
 
 	/* Calling busy in a loop should be enough to flush the rendering */
-- 
2.14.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

             reply	other threads:[~2019-05-29 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 13:53 Tomasz Lis [this message]
2019-05-29 14:46 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/prime_busy: Increase timeout to mind pre-silicon Patchwork
2019-05-29 23:12 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-05-31 10:23 ` [igt-dev] [PATCH i-g-t] " Katarzyna Dec

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=20190529135332.3099-1-tomasz.lis@intel.com \
    --to=tomasz.lis@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