From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v5 2/7] lib/igt_core: use the macro when checking for list_subtests
Date: Mon, 10 Jul 2023 13:53:49 +0200 [thread overview]
Message-ID: <20230710115354.699245-3-mauro.chehab@linux.intel.com> (raw)
In-Reply-To: <20230710115354.699245-1-mauro.chehab@linux.intel.com>
From: Mauro Carvalho Chehab <mchehab@kernel.org>
We're implementing a new argument to display all tests. Before
doing that, make the check for it more generic to prepare for
the changes.
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
lib/igt_core.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lib/igt_core.c b/lib/igt_core.c
index 3ee3a01c3668..9a0029d294a8 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -870,7 +870,7 @@ static void print_version(void)
{
struct utsname uts;
- if (list_subtests)
+ if (igt_only_list_subtests())
return;
uname(&uts);
@@ -1198,12 +1198,12 @@ static int common_init(int *argc, char **argv,
break;
case OPT_RUN_SUBTEST:
assert(optarg);
- if (!list_subtests)
+ if (!igt_only_list_subtests())
run_single_subtest = strdup(optarg);
break;
case OPT_RUN_DYNAMIC_SUBTEST:
assert(optarg);
- if (!list_subtests)
+ if (!igt_only_list_subtests())
run_single_dynamic_subtest = strdup(optarg);
break;
case OPT_DESCRIPTION:
@@ -1265,7 +1265,7 @@ out:
/* exit with no error for -h/--help */
exit(ret == -1 ? 0 : IGT_EXIT_INVALID);
- if (!list_subtests) {
+ if (!igt_only_list_subtests()) {
bind_fbcon(false);
igt_kmsg(KMSG_INFO "%s: executing\n", command_str);
print_version();
@@ -3098,7 +3098,7 @@ void igt_vlog(const char *domain, enum igt_log_level level, const char *format,
if (!thread_id)
return;
- if (list_subtests && level <= IGT_LOG_WARN)
+ if (igt_only_list_subtests() && level <= IGT_LOG_WARN)
return;
if (vasprintf(&line, format, args) == -1)
--
2.40.1
next prev parent reply other threads:[~2023-07-10 11:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 11:53 [igt-dev] [PATCH i-g-t v5 0/7] Speedup IGT build time Mauro Carvalho Chehab
2023-07-10 11:53 ` [igt-dev] [PATCH i-g-t v5 1/7] tests/meson.build: Simplify builds for core and i915 targets Mauro Carvalho Chehab
2023-07-10 17:51 ` Kamil Konieczny
2023-07-10 11:53 ` Mauro Carvalho Chehab [this message]
2023-07-10 17:58 ` [igt-dev] [PATCH i-g-t v5 2/7] lib/igt_core: use the macro when checking for list_subtests Kamil Konieczny
2023-07-10 11:53 ` [igt-dev] [PATCH i-g-t v5 3/7] lib/igt_core: add an option to show the testlist Mauro Carvalho Chehab
2023-07-10 18:11 ` Kamil Konieczny
2023-07-10 11:53 ` [igt-dev] [PATCH i-g-t v5 4/7] tests/meson.build: create testlists for tests Mauro Carvalho Chehab
2023-07-10 18:17 ` Kamil Konieczny
2023-08-30 21:41 ` Mark Yacoub
[not found] ` <CAAea8Y3a_RjknGcn6-v9CVUVpcmMuASnJKfn73KGtQzbXo0TcA@mail.gmail.com>
2023-08-31 9:28 ` Mauro Carvalho Chehab
[not found] ` <CAAea8Y13=CguTipLJjJJt_pBvaiv92DViWJBZwvtjm7W-SU+vw@mail.gmail.com>
2023-09-01 7:45 ` Mauro Carvalho Chehab
2023-09-01 8:34 ` Mauro Carvalho Chehab
2023-09-01 11:01 ` Mauro Carvalho Chehab
[not found] ` <CAAea8Y2hX2=TjXmGJN=tFBSgFPqe8J5EgDCkoR7OMVy+J2t+cA@mail.gmail.com>
2023-09-04 6:53 ` Mauro Carvalho Chehab
2023-07-10 11:53 ` [igt-dev] [PATCH i-g-t v5 5/7] scripts/test_list.py: speedup testlist check logic Mauro Carvalho Chehab
2023-07-10 18:23 ` Kamil Konieczny
2023-07-10 11:53 ` [igt-dev] [PATCH i-g-t v5 6/7] tests/build: Generate and store an intel-ci.testlist Mauro Carvalho Chehab
2023-07-10 18:26 ` Kamil Konieczny
2023-07-10 11:53 ` [igt-dev] [PATCH i-g-t v5 7/7] scripts/test_list.py: optimize check regex Mauro Carvalho Chehab
2023-07-10 18:27 ` Kamil Konieczny
2023-07-10 13:50 ` [igt-dev] ✓ Fi.CI.BAT: success for Speedup IGT build time Patchwork
2023-07-10 14:00 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-07-10 17:02 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-31 11:36 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Speedup IGT build time (rev2) 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=20230710115354.699245-3-mauro.chehab@linux.intel.com \
--to=mauro.chehab@linux.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