From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf test: Add a runs-per-test flag
Date: Mon, 11 Nov 2024 10:51:59 -0500 [thread overview]
Message-ID: <bfba7266-1903-41ca-9961-aa449f982912@linux.intel.com> (raw)
In-Reply-To: <20241109160219.49976-1-irogers@google.com>
On 2024-11-09 11:02 a.m., Ian Rogers wrote:
> To detect flakes it is useful to run tests more than once. Add a
> runs-per-test flag that will run each test multiple times.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/tests/builtin-test.c | 38 ++++++++++++++++++++-------------
> 1 file changed, 23 insertions(+), 15 deletions(-)
>
> diff --git a/tools/perf/tests/builtin-test.c b/tools/perf/tests/builtin-test.c
> index d2cabaa8ad92..574fbd5caff0 100644
> --- a/tools/perf/tests/builtin-test.c
> +++ b/tools/perf/tests/builtin-test.c
> @@ -42,6 +42,8 @@
> static bool dont_fork;
> /* Fork the tests in parallel and wait for their completion. */
> static bool sequential;
> +/* Numer of times each test is run. */
> +static unsigned int runs_per_test = 1;
> const char *dso_to_test;
> const char *test_objdump_path = "objdump";
>
> @@ -490,10 +492,10 @@ static int __cmd_test(struct test_suite **suites, int argc, const char *argv[],
> len = strlen(test_description(*t, subi));
> if (width < len)
> width = len;
> - num_tests++;
> + num_tests += runs_per_test;
> }
> } else {
> - num_tests++;
> + num_tests += runs_per_test;
> }
> }
Seems we just need to calculate the num_tests once at the end for each
loop. Something as below may works. (not tested)
@@ -482,20 +490,19 @@ static int __cmd_test(struct test_suite **suites,
int argc, const char *argv[],
for (struct test_suite **t = suites; *t; t++) {
int len = strlen(test_description(*t, -1));
+ int subi = 0, subn = 1;
if (width < len)
width = len;
if (has_subtests(*t)) {
- for (int subi = 0, subn = num_subtests(*t); subi
< subn; subi++) {
+ for (subn = num_subtests(*t); subi < subn; subi++) {
len = strlen(test_description(*t, subi));
if (width < len)
width = len;
- num_tests++;
}
- } else {
- num_tests++;
}
+ num_tests += subn * runs_per_test;
}
child_tests = calloc(num_tests, sizeof(*child_tests));
if (!child_tests)
> child_tests = calloc(num_tests, sizeof(*child_tests));
> @@ -556,21 +558,25 @@ static int __cmd_test(struct test_suite **suites, int argc, const char *argv[],
> }
>
> if (!has_subtests(*t)) {
> - err = start_test(*t, curr, -1, &child_tests[child_test_num++],
> - width, pass);
> - if (err)
> - goto err_out;
> + for (unsigned int run = 0; run < runs_per_test; run++) {
> + err = start_test(*t, curr, -1, &child_tests[child_test_num++],
> + width, pass);
> + if (err)
> + goto err_out;
> + }
> continue;
> }
> - for (int subi = 0, subn = num_subtests(*t); subi < subn; subi++) {
> - if (!perf_test__matches(test_description(*t, subi),
> - curr, argc, argv))
> - continue;
> -
> - err = start_test(*t, curr, subi, &child_tests[child_test_num++],
> - width, pass);
> - if (err)
> - goto err_out;
> + for (unsigned int run = 0; run < runs_per_test; run++) {
> + for (int subi = 0, subn = num_subtests(*t); subi < subn; subi++) {
> + if (!perf_test__matches(test_description(*t, subi),
> + curr, argc, argv))
> + continue;
> +
> + err = start_test(*t, curr, subi, &child_tests[child_test_num++],
> + width, pass);
> + if (err)
> + goto err_out;
> + }
Can we add a wrapper for the start_test()? Something similar to below?
It avoids adding the loop for every places using the start_test.
+static int start_test(struct test_suite *test, int i, int subi, struct
child_test **child,
+ int width, int pass)
+{
+ for (unsigned int run = 0; run < runs_per_test; run++) {
+ __start_test();
+ }
+}
Thanks,
Kan
> }
> }
> if (!sequential) {
> @@ -714,6 +720,8 @@ int cmd_test(int argc, const char **argv)
> "Do not fork for testcase"),
> OPT_BOOLEAN('S', "sequential", &sequential,
> "Run the tests one after another rather than in parallel"),
> + OPT_UINTEGER('r', "runs-per-test", &runs_per_test,
> + "Run each test the given number of times, default 1"),
> OPT_STRING('w', "workload", &workload, "work", "workload to run for testing, use '--list-workloads' to list the available ones."),
> OPT_BOOLEAN(0, "list-workloads", &list_workloads, "List the available builtin workloads to use with -w/--workload"),
> OPT_STRING(0, "dso", &dso_to_test, "dso", "dso to test"),
next prev parent reply other threads:[~2024-11-11 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 16:02 [PATCH v1] perf test: Add a runs-per-test flag Ian Rogers
2024-11-11 15:51 ` Liang, Kan [this message]
2024-11-11 16:10 ` Ian Rogers
2024-11-11 17:14 ` Liang, Kan
2024-11-11 17:26 ` Ian Rogers
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=bfba7266-1903-41ca-9961-aa449f982912@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).