From: Derek Morton <derek.j.morton@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch
Subject: [PATCH i-g-t] lib/igt_core.c: Add partial match functionality to run-subtests
Date: Fri, 19 Feb 2016 10:31:31 +0000 [thread overview]
Message-ID: <1455877891-25291-1-git-send-email-derek.j.morton@intel.com> (raw)
Add the ability to specify a substring of the subtest using --run-subtests.
This allows 'string' to be used as an abbreviation of the wildcard expression
'*string*' when defining which subtests should run.
Signed-off-by: Derek Morton <derek.j.morton@intel.com>
---
lib/igt_core.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/lib/igt_core.c b/lib/igt_core.c
index 8e0bd2e..1e31a25 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -215,7 +215,7 @@
* description of allowed wildcard expressions.
* Some examples of allowed wildcard expressions are:
*
- * - '*basic*' match any subtest containing basic
+ * - '*basic*' match any subtest containing basic. This expression may be abbreviated to just 'basic'.
* - 'basic-???' match any subtest named basic- with 3 characters after -
* - 'basic-[0-9]' match any subtest named basic- with a single number after -
* - 'basic-[^0-9]' match any subtest named basic- with a single non numerical character after -
@@ -827,7 +827,8 @@ bool __igt_run_subtest(const char *subtest_name)
}
if (run_single_subtest) {
- if (uwildmat(subtest_name, run_single_subtest) == 0)
+ if ((uwildmat(subtest_name, run_single_subtest) == 0) &&
+ (NULL == strstr(subtest_name, run_single_subtest)))
return false;
else
run_single_subtest_found = true;
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2016-02-19 10:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1455877891-25291-1-git-send-email-derek.j.morton@intel.com \
--to=derek.j.morton@intel.com \
--cc=daniel.vetter@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).