From: Gabriel Feceoru <gabriel.feceoru@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch, marius.vlad@intel.com
Subject: [PATCH i-g-t] tests: Separate tests with lots of subtests
Date: Mon, 18 Apr 2016 12:52:44 +0300 [thread overview]
Message-ID: <1460973164-26480-1-git-send-email-gabriel.feceoru@intel.com> (raw)
Currently, when trying to run i-g-t tests with piglit, it takes up
to 20s until the first test is executed.
The main reason is that gem_concurrent_all has ~500k subtests,
overkilling piglit.
This patch separates gem_concurrent_* tests from the rest of the tests,
creating two files test-list.txt and test-list-full.txt.
The piglit can now enumerate the i-g-t tests within a decent few seconds.
The second list could be used when trying to execute specific these tests.
Signed-off-by: Gabriel Feceoru <gabriel.feceoru@intel.com>
---
tests/Makefile.am | 6 ++++++
tests/Makefile.sources | 22 ++++++++++++++++++++--
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/tests/Makefile.am b/tests/Makefile.am
index 771e9ee..185962b 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -14,6 +14,12 @@ test-list.txt: Makefile.sources
@echo ${single_kernel_tests} ${multi_kernel_tests} >> $@
@echo END TESTLIST >> $@
+test-list-full.txt: Makefile.sources
+ @echo TESTLIST > $@
+ @echo ${single_kernel_tests} ${multi_kernel_tests} ${extra_multi_kernel_tests} >> $@
+ @echo END TESTLIST >> $@
+
+
noinst_PROGRAMS = \
$(HANG) \
$(TESTS_testsuite) \
diff --git a/tests/Makefile.sources b/tests/Makefile.sources
index c52be2c..ca72243 100644
--- a/tests/Makefile.sources
+++ b/tests/Makefile.sources
@@ -20,8 +20,6 @@ TESTS_progs_M = \
gem_busy \
gem_caching \
gem_close_race \
- gem_concurrent_blit \
- gem_concurrent_all \
gem_create \
gem_cs_tlb \
gem_ctx_param_basic \
@@ -117,6 +115,11 @@ TESTS_progs_M = \
template \
$(NULL)
+TESTS_progs_XM = \
+ gem_concurrent_blit \
+ gem_concurrent_all \
+ $(NULL)
+
TESTS_progs = \
core_auth \
core_getclient \
@@ -219,6 +222,15 @@ multi_kernel_tests = \
$(TESTS_scripts_M) \
$(NULL)
+
+# This target contains testcases with lots of subtests.
+# It was split from multi_kernel_tests because of the overhead of listing all
+# the subtests in piglit
+extra_multi_kernel_tests = \
+ $(TESTS_progs_XM) \
+ $(NULL)
+
+
# This target is for simple testcase which don't expose any subtest.
#
# Your testcase should probably use igt_simple_main, but none of the other magic
@@ -233,6 +245,12 @@ kernel_tests = \
$(multi_kernel_tests) \
$(NULL)
+kernel_tests_full = \
+ $(single_kernel_tests) \
+ $(multi_kernel_tests) \
+ $(extra_multi_kernel_tests) \
+ $(NULL)
+
# Test that exercise specific asserts in the test framework library and are
# hence expected to fail.
XFAIL_TESTS = \
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-04-18 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 9:52 Gabriel Feceoru [this message]
2016-04-20 13:04 ` [PATCH i-g-t] tests: Separate tests with lots of subtests Daniel Vetter
2016-04-20 14:21 ` [PATCH i-g-t v2] " Gabriel Feceoru
2016-05-17 9:59 ` Daniel Vetter
2016-05-17 11:31 ` Gabriel Feceoru
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=1460973164-26480-1-git-send-email-gabriel.feceoru@intel.com \
--to=gabriel.feceoru@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marius.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox