From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [i-g-t V4 1/7] testplan/i915: Exclude non-i915 tests from i915 testplan
Date: Thu, 3 Aug 2023 01:03:24 +0530 [thread overview]
Message-ID: <20230802193330.3843896-2-bhanuprakash.modem@intel.com> (raw)
In-Reply-To: <20230802193330.3843896-1-bhanuprakash.modem@intel.com>
Using wildcards in testplan configs, and keeping other configs
(Xe & kms) in same dir may leads to the problem. Hence, exclude
non-i915 tests from i915 testplan.
Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
tests/i915/i915_test_config.json | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/i915/i915_test_config.json b/tests/i915/i915_test_config.json
index a029801a6..c15ef2580 100644
--- a/tests/i915/i915_test_config.json
+++ b/tests/i915/i915_test_config.json
@@ -12,7 +12,8 @@
"../prime_vgem.c", "../sw_sync.c", "../syncobj_basic.c",
"../syncobj_timeline.c", "../syncobj_wait.c",
"../vgem_basic.c", "../vgem_slow.c" ],
- "exclude_files": [ "kms_*", "gem_concurrent_all.c", "gem_concurrent_blit.c" ],
+ "exclude_files": [ "kms_*", "gem_concurrent_all.c", "gem_concurrent_blit.c",
+ "xe_*" ],
"fields": {
"Mega feature": {
"_properties_": {
--
2.40.0
next prev parent reply other threads:[~2023-08-02 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 19:33 [igt-dev] [i-g-t V4 0/7] New dir structure for intel specific tests Bhanuprakash Modem
2023-08-02 19:33 ` Bhanuprakash Modem [this message]
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 2/7] testplan/kms: Move kms testplan to intel dir Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 3/7] tests/i915/prime_mmap_kms: Add missing documentation Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 4/7] tests/meson.build: Simplify builds for Chamelium targets Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 5/7] tests: Move intel specific tests to new directory Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 6/7] tests/meson.build: Split intel targets based on their nature Bhanuprakash Modem
2023-08-02 19:33 ` [igt-dev] [i-g-t V4 7/7] tests: Rename all intel specific tests Bhanuprakash Modem
2023-08-02 20:31 ` [igt-dev] ○ CI.xeBAT: info for New dir structure for intel specific tests (rev7) Patchwork
2023-08-02 20:40 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-30 14:44 ` [igt-dev] [i-g-t V4 0/7] New dir structure for intel specific tests Mauro Carvalho Chehab
2023-08-31 15:33 ` Modem, Bhanuprakash
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=20230802193330.3843896-2-bhanuprakash.modem@intel.com \
--to=bhanuprakash.modem@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