From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [CI 2/2] gem_exec_fence: Really loop through all engines
Date: Thu, 14 Mar 2019 12:27:40 +0200 [thread overview]
Message-ID: <20190314102740.5243-2-petri.latvala@intel.com> (raw)
In-Reply-To: <20190314102740.5243-1-petri.latvala@intel.com>
Continue instead of breaking on the first engine.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
---
tests/i915/gem_exec_fence.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/i915/gem_exec_fence.c b/tests/i915/gem_exec_fence.c
index ba46595d..c6661626 100644
--- a/tests/i915/gem_exec_fence.c
+++ b/tests/i915/gem_exec_fence.c
@@ -274,7 +274,7 @@ static void test_fence_busy_all(int fd, unsigned flags)
if (all < 0) {
all = fence;
- break;
+ continue;
}
new = sync_fence_merge(all, fence);
--
2.19.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-14 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 10:27 [igt-dev] [CI 1/2] lib/sw_sync: Fix querying fence status Petri Latvala
2019-03-14 10:27 ` Petri Latvala [this message]
2019-03-14 11:15 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [CI,1/2] " Patchwork
2019-03-14 12:51 ` Patchwork
2019-03-14 19:35 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-08-12 12:36 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [CI,1/2] lib/sw_sync: Fix querying fence status (rev2) Patchwork
2019-08-12 17:38 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-08-12 17:44 ` [igt-dev] [CI 1/2] lib/sw_sync: Fix querying fence status Matthew Auld
2019-08-12 17:47 ` Chris Wilson
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=20190314102740.5243-2-petri.latvala@intel.com \
--to=petri.latvala@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