From: robert.foss@collabora.com
To: intel-gfx@lists.freedesktop.org,
Gustavo Padovan <gustavo.padovan@collabora.com>,
Daniel Stone <daniels@collabora.com>,
Daniel Vetter <daniel@ffwll.ch>,
Marius Vlad <marius.c.vlad@intel.com>,
Eric Engestrom <eric@engestrom.ch>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: [PATCH i-g-t v4 04/13] tests/sw_sync: Add subtest test_alloc_fence_invalid_timeline
Date: Wed, 14 Sep 2016 11:04:33 -0400 [thread overview]
Message-ID: <20160914150442.18183-5-robert.foss@collabora.com> (raw)
In-Reply-To: <20160914150442.18183-1-robert.foss@collabora.com>
From: Robert Foss <robert.foss@collabora.com>
This subtests tests that creating fences on negative timelines fail.
Signed-off-by: Robert Foss <robert.foss@collabora.com>
Reviewed-by: Eric Engestrom <eric@engestrom.ch>
---
tests/sw_sync.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tests/sw_sync.c b/tests/sw_sync.c
index 8f6208b..75bd471 100644
--- a/tests/sw_sync.c
+++ b/tests/sw_sync.c
@@ -56,6 +56,10 @@ static void test_alloc_fence(void)
close(timeline);
}
+static void test_alloc_fence_invalid_timeline(void)
+{
+ igt_assert(__sw_sync_fence_create(-1, 0) < 0);
+}
igt_main
{
@@ -64,5 +68,8 @@ igt_main
igt_subtest("alloc_fence")
test_alloc_fence();
+
+ igt_subtest("alloc_fence_invalid_timeline")
+ test_alloc_fence_invalid_timeline();
}
--
2.9.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-09-14 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 15:04 [PATCH i-g-t v4 00/13] Implement sw_sync test robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 01/13] lib/sw_sync: Add helper functions for managing synchronization primitives robert.foss
2016-09-15 6:46 ` Chris Wilson
2016-09-15 18:35 ` Robert Foss
2016-09-15 19:28 ` Robert Foss
2016-09-15 19:36 ` Gustavo Padovan
2016-09-14 15:04 ` [PATCH i-g-t v4 02/13] tests/sw_sync: Add sw_sync test robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 03/13] tests/sw_sync: Add subtest test_alloc_fence robert.foss
2016-09-14 15:04 ` robert.foss [this message]
2016-09-14 15:04 ` [PATCH i-g-t v4 05/13] tests/sw_sync: Add subtest test_alloc_merge_fence robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 06/13] tests/sw_sync: Add subtest test_sync_wait robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 07/13] tests/sw_sync: Add subtest test_sync_merge robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 08/13] tests/sw_sync: Add subtest test_sync_merge_same robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 09/13] tests/sw_sync: Add subtest test_sync_multi_consumer robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 10/13] tests/sw_sync: Add subtest test_sync_multi_consumer_producer robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 11/13] tests/sw_sync: Add subtest test_sync_random_merge robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 12/13] tests/sw_sync: Add subtest test_sync_multi_timeline_wait robert.foss
2016-09-14 15:04 ` [PATCH i-g-t v4 13/13] tests/sw_sync: Add subtest test_sync_multi_producer_single_consumer robert.foss
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=20160914150442.18183-5-robert.foss@collabora.com \
--to=robert.foss@collabora.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=eric@engestrom.ch \
--cc=gustavo.padovan@collabora.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marius.c.vlad@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.