From: Damien Lespiau <damien.lespiau@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t 3/5] tests: Use IGT_SIMULATION to tune the list of tests to run
Date: Tue, 26 Mar 2013 15:24:37 +0000 [thread overview]
Message-ID: <1364311479-20669-4-git-send-email-damien.lespiau@intel.com> (raw)
In-Reply-To: <1364311479-20669-1-git-send-email-damien.lespiau@intel.com>
There are two ways to run tests, directly with make check/test
or through piglit.
When IGT_SIMULATION is set to '1', we substitute the list of tests in
those two code paths with carefully selected tests. The stress tests and
other horrors are left to torture the real hardware as they don't make
too much sense in simulation.
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
---
tests/Makefile.am | 43 ++++++++++++++++++++++++++++++++++++++++---
1 file changed, 40 insertions(+), 3 deletions(-)
diff --git a/tests/Makefile.am b/tests/Makefile.am
index 2fddfe8..33db962 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -137,22 +137,59 @@ kernel_tests = \
$(multi_kernel_tests) \
$(NULL)
+# We maintain here a list of tests to run in our simulation environments
+single_simulation_tests = \
+ gem_mmap \
+ gem_pread_after_blit \
+ gem_ring_sync_loop \
+ gem_ctx_basic \
+ gem_pipe_control_store_loop \
+ gem_storedw_loop_render \
+ gem_storedw_loop_blt \
+ gem_storedw_loop_bsd \
+ gem_render_linear_blits \
+ gem_tiled_blits \
+ gem_cpu_reloc \
+ $(NULL)
+
+multi_simulation_tests = \
+ gem_exec_nop \
+ gem_mmap_gtt \
+ $(NULL)
+
+simulation_tests = \
+ $(single_simulation_tests) \
+ $(multi_simulation_tests) \
+ $(NULL)
+
TESTS = \
$(NULL)
test:
@whoami | grep root || ( echo ERROR: not running as root; exit 1 )
@./check_drm_clients
- @make TESTS="${kernel_tests}" check
+ @if [ "${IGT_SIMULATION}" == 1 ]; then \
+ make TESTS="${simulation_tests}" check; \
+ else \
+ make TESTS="${kernel_tests}" check; \
+ fi
list-single-tests:
@echo TESTLIST
- @echo ${single_kernel_tests}
+ @if [ "${IGT_SIMULATION}" == 1 ]; then \
+ echo ${single_simulation_tests}; \
+ else \
+ echo ${single_kernel_tests}; \
+ fi
@echo END TESTLIST
list-multi-tests:
@echo TESTLIST
- @echo ${multi_kernel_tests}
+ @if [ "${IGT_SIMULATION}" == 1 ]; then \
+ echo ${multi_simulation_tests}; \
+ else \
+ echo ${multi_kernel_tests}; \
+ fi
@echo END TESTLIST
HANG = \
--
1.7.11.7
next prev parent reply other threads:[~2013-03-26 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 15:24 Craft a list of tests to run in simulation (and tune them) Damien Lespiau
2013-03-26 15:24 ` [PATCH i-g-t 1/5] README: Reword a few sentences Damien Lespiau
2013-03-26 15:24 ` [PATCH i-g-t 2/5] lib: Rename IGT_QUICK to IGT_SIMULATION Damien Lespiau
2013-03-26 15:24 ` Damien Lespiau [this message]
2013-03-26 15:38 ` [PATCH i-g-t 3/5] tests: Use IGT_SIMULATION to tune the list of tests to run Daniel Vetter
2013-03-26 17:00 ` Ben Widawsky
2013-03-27 0:24 ` Daniel Vetter
2013-03-27 2:54 ` Sun, Yi
2013-04-01 7:21 ` Sun, Yi
2013-04-02 17:06 ` Ben Widawsky
2013-04-02 17:16 ` Damien Lespiau
2013-04-02 17:38 ` Daniel Vetter
2013-03-26 15:24 ` [PATCH i-g-t 4/5] tests: Instrument tests run in simulation to run quickly Damien Lespiau
2013-03-26 15:24 ` [PATCH i-g-t 5/5] build: Make grep silent with running make test Damien Lespiau
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=1364311479-20669-4-git-send-email-damien.lespiau@intel.com \
--to=damien.lespiau@intel.com \
--cc=intel-gfx@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 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.