From: Petri Latvala <petri.latvala@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: [igt-dev] [PATCH i-g-t 10/10] i915/gem_exec_basic: Use dynamic subtests
Date: Fri, 16 Aug 2019 12:34:26 +0300 [thread overview]
Message-ID: <20190816093426.10644-11-petri.latvala@intel.com> (raw)
In-Reply-To: <20190816093426.10644-1-petri.latvala@intel.com>
Instead of generating a subtest for each engine in a static list,
convert to dynamic subtests, with one dynamic subtest per actually
present physical engine.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
---
tests/i915/gem_exec_basic.c | 26 +++++++++++++++++++-------
1 file changed, 19 insertions(+), 7 deletions(-)
diff --git a/tests/i915/gem_exec_basic.c b/tests/i915/gem_exec_basic.c
index 1287860b..a1d1922b 100644
--- a/tests/i915/gem_exec_basic.c
+++ b/tests/i915/gem_exec_basic.c
@@ -159,13 +159,25 @@ igt_main
igt_subtest("gtt-all")
gtt_all(fd);
- __for_each_physical_engine(fd, e) {
- igt_subtest_f("basic-%s", e->name)
- noop(fd, e->flags);
- igt_subtest_f("readonly-%s", e->name)
- readonly(fd, e->flags);
- igt_subtest_f("gtt-%s", e->name)
- gtt(fd, e->flags);
+ igt_dynamic_subtest_container("basic") {
+ __for_each_physical_engine(fd, e) {
+ igt_dynamic_subtest_f("%s", e->name)
+ noop(fd, e->flags);
+ }
+ }
+
+ igt_dynamic_subtest_container("readonly") {
+ __for_each_physical_engine(fd, e) {
+ igt_dynamic_subtest_f("%s", e->name)
+ readonly(fd, e->flags);
+ }
+ }
+
+ igt_dynamic_subtest_container("gtt") {
+ __for_each_physical_engine(fd, e) {
+ igt_dynamic_subtest_f("%s", e->name)
+ gtt(fd, e->flags);
+ }
}
igt_fixture {
--
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-08-16 9:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 9:34 [igt-dev] [PATCH i-g-t 00/10] Dynamic subtests, v2 Petri Latvala
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 01/10] lib: Introduce dynamic subtests Petri Latvala
2019-08-28 10:16 ` Arkadiusz Hiler
2019-08-28 10:30 ` Petri Latvala
2019-08-28 10:38 ` Arkadiusz Hiler
2019-08-28 12:58 ` Petri Latvala
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 02/10] lib/tests: Unit tests for " Petri Latvala
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 03/10] lib/tests: Test that igt_describe works with " Petri Latvala
2019-08-28 12:33 ` Arkadiusz Hiler
2019-08-28 12:39 ` Petri Latvala
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 04/10] runner/resultgen: Refactor output parsing Petri Latvala
2019-08-28 11:48 ` Arkadiusz Hiler
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 05/10] runner/json_tests: Adapt to better " Petri Latvala
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 06/10] runner: Parse dynamic subtest outputs and results Petri Latvala
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 07/10] runner/json_tests: Test dynamic subtests Petri Latvala
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 08/10] kms_plane_cursor: Use " Petri Latvala
2019-08-16 9:34 ` [igt-dev] [PATCH i-g-t 09/10] perf_pmu: " Petri Latvala
2019-08-16 9:34 ` Petri Latvala [this message]
2019-08-16 10:17 ` [igt-dev] ✓ Fi.CI.BAT: success for Dynamic subtests (rev2) Patchwork
2019-08-16 22:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20190816093426.10644-11-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