From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t 4/4] tests/gem_lmem_swapping: reduce the timeout
Date: Fri, 25 Mar 2022 08:21:29 +0100 [thread overview]
Message-ID: <56b125e7-7fd6-4a9f-c37f-c99a5544d18b@linux.intel.com> (raw)
In-Reply-To: <20220324142621.347452-5-matthew.auld@intel.com>
On 3/24/22 15:26, Matthew Auld wrote:
> 300s is way too much for some BAT test. Drop it down to 45s.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Nirmoy Das <nirmoy.das@linux.intel.com>
> ---
> tests/i915/gem_lmem_swapping.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/i915/gem_lmem_swapping.c b/tests/i915/gem_lmem_swapping.c
> index ad1c989c..6c47bff2 100644
> --- a/tests/i915/gem_lmem_swapping.c
> +++ b/tests/i915/gem_lmem_swapping.c
> @@ -219,7 +219,7 @@ static void __do_evict(int i915,
> * For TEST_MULTI runs, make each object counts a loop to
> * avoid excessive run times.
> */
> - for (l = 0; l < params->loops && igt_seconds_elapsed(&t) < 300; l += num) {
> + for (l = 0; l < params->loops && igt_seconds_elapsed(&t) < 45; l += num) {
> unsigned int idx = rand() % params->count;
>
> num = params->flags & TEST_MULTI ? rand() % max_swap_in + 1 : 1;
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
prev parent reply other threads:[~2022-03-25 7:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 14:26 [Intel-gfx] [PATCH i-g-t 0/4] Some gem_lmem_swapping tweaks Matthew Auld
2022-03-24 14:26 ` [Intel-gfx] [PATCH i-g-t 1/4] test/gem_lmem_swapping: account for object rounding Matthew Auld
2022-03-24 17:25 ` Dixit, Ashutosh
2022-03-25 8:05 ` Thomas Hellström
2022-03-24 14:26 ` [Intel-gfx] [PATCH i-g-t 2/4] test/gem_lmem_swapping: fix physical engine usage Matthew Auld
2022-03-24 14:46 ` Tvrtko Ursulin
2022-03-24 17:39 ` [Intel-gfx] [igt-dev] " Dixit, Ashutosh
2022-03-24 14:26 ` [Intel-gfx] [PATCH i-g-t 3/4] tests/gem_lmem_swapping: limit lmem to 4G Matthew Auld
2022-03-24 14:33 ` Thomas Hellström
2022-03-24 17:47 ` [Intel-gfx] [igt-dev] " Dixit, Ashutosh
2022-03-25 8:40 ` Matthew Auld
2022-03-25 10:02 ` Petri Latvala
2022-03-25 10:13 ` [Intel-gfx] " Das, Nirmoy
2022-03-25 10:18 ` [Intel-gfx] [igt-dev] " Petri Latvala
2022-03-25 10:20 ` Matthew Auld
2022-03-24 14:26 ` [Intel-gfx] [PATCH i-g-t 4/4] tests/gem_lmem_swapping: reduce the timeout Matthew Auld
2022-03-25 7:21 ` Thomas Hellström [this message]
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=56b125e7-7fd6-4a9f-c37f-c99a5544d18b@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox