From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@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>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] perf test: Add a runs-per-test flag
Date: Wed, 8 Jan 2025 11:09:30 -0800 [thread overview]
Message-ID: <Z37NaqivQSrclaTd@google.com> (raw)
In-Reply-To: <20250107220152.1213959-4-irogers@google.com>
On Tue, Jan 07, 2025 at 02:01:52PM -0800, 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.
Does it change the output? What if it sometimes succeeds and fails?
It'd be nice if you can add an example output in the commit log.
Also please update the documentation.
Thanks,
Namhyung
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/tests/builtin-test.c | 28 +++++++++++++++++-----------
> 1 file changed, 17 insertions(+), 11 deletions(-)
>
> diff --git a/tools/perf/tests/builtin-test.c b/tools/perf/tests/builtin-test.c
> index 887f735da900..729740c1e5e5 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;
> +/* Number of times each test is run. */
> +static unsigned int runs_per_test = 1;
> const char *dso_to_test;
> const char *test_objdump_path = "objdump";
>
> @@ -485,7 +487,7 @@ static int __cmd_test(struct test_suite **suites, int argc, const char *argv[],
> len = strlen(test_description(*t, i));
> if (width < len)
> width = len;
> - num_tests++;
> + num_tests += runs_per_test;
> }
> }
> child_tests = calloc(num_tests, sizeof(*child_tests));
> @@ -549,16 +551,18 @@ static int __cmd_test(struct test_suite **suites, int argc, const char *argv[],
> continue;
> }
>
> - test_suite__for_each_test_case(*t, curr_test_case) {
> - if (!perf_test__matches(test_description(*t, curr_test_case),
> - curr_suite, argc, argv))
> - continue;
> -
> - err = start_test(*t, curr_suite, curr_test_case,
> - &child_tests[child_test_num++],
> - width, pass);
> - if (err)
> - goto err_out;
> + for (unsigned int run = 0; run < runs_per_test; run++) {
> + test_suite__for_each_test_case(*t, curr_test_case) {
> + if (!perf_test__matches(test_description(*t, curr_test_case),
> + curr_suite, argc, argv))
> + continue;
> +
> + err = start_test(*t, curr_suite, curr_test_case,
> + &child_tests[child_test_num++],
> + width, pass);
> + if (err)
> + goto err_out;
> + }
> }
> }
> if (!sequential) {
> @@ -698,6 +702,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"),
> --
> 2.47.1.613.gc27f4b7a9f-goog
>
prev parent reply other threads:[~2025-01-08 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 22:01 [PATCH v2 0/3] Add a runs-per-test flag Ian Rogers
2025-01-07 22:01 ` [PATCH v2 1/3] perf test: Rename functions and variables for better clarity Ian Rogers
2025-01-07 22:01 ` [PATCH v2 2/3] perf test: Send list output to stdout rather than stderr Ian Rogers
2025-01-07 22:01 ` [PATCH v2 3/3] perf test: Add a runs-per-test flag Ian Rogers
2025-01-08 19:09 ` Namhyung Kim [this message]
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=Z37NaqivQSrclaTd@google.com \
--to=namhyung@kernel.org \
--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=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--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).