From: Ian Rogers <irogers@google.com>
To: 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>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>,
Howard Chu <howardchu95@gmail.com>,
Athira Jajeev <atrajeev@linux.vnet.ibm.com>,
Michael Petlan <mpetlan@redhat.com>,
Veronika Molnarova <vmolnaro@redhat.com>,
Dapeng Mi <dapeng1.mi@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
Colin Ian King <colin.i.king@gmail.com>,
Weilin Wang <weilin.wang@intel.com>,
Andi Kleen <ak@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH v2 0/8] Run tests in parallel showing number of tests running
Date: Fri, 11 Oct 2024 15:03:46 -0700 [thread overview]
Message-ID: <20241011220354.756798-1-irogers@google.com> (raw)
Avoid waitpid so that stdout/stderr aren't destroyed prior to wanting
to read them for display. When running on a color terminal, display
the number of running tests (1 if sequential). To avoid previous
flicker, only delete and refresh the display line when it changes. An
earlier version of this code is here:
https://lore.kernel.org/lkml/20240701044236.475098-1-irogers@google.com/
Add a signal handler for perf tests so that unexpected signals are
displayed and test clean up is possible.
In perf test add an "exclusive" flag that causes a test to be run with
no other test. Set this flag manually for C tests and via a
"(exclusive)" in the test description for shell tests. Add the flag to
shell tests that may fail when run with other tests.
Change the perf test loop to run in two passes. For parallel
execution, the first pass runs all tests that can be run in parallel
then the 2nd runs remaining tests sequentially. This causes the
"exclusive" tests to be run last and with test numbers moderately out
of alignment.
Change the default to be to run tests in parallel. Running tests in
parallel brings the execution time down to less than half.
v2: Fix inaccurate remaining counts when running specific
tests. Rename "remaining" to "active" to better reflect the
testing behavior. Move the exclusive flag to test cases and not
entire suites. Add more "(exclusive)" flags to test as
suggested-by James Clark. Remove "(exclusive)" flag from test
descriptions to keep the command line output more concise. Add
James Clark's tested-by.
Ian Rogers (8):
tools subcmd: Add non-waitpid check_if_command_finished()
perf test: Display number of active running tests
perf test: Reduce scope of parallel variable
perf test: Avoid list test blocking on writing to stdout
perf test: Tag parallel failing shell tests with "(exclusive)"
perf test: Add a signal handler around running a test
perf test: Run parallel tests in two passes
perf test: Make parallel testing the default
tools/lib/subcmd/run-command.c | 33 +++
tools/perf/tests/builtin-test.c | 274 ++++++++++++------
.../tests/shell/coresight/asm_pure_loop.sh | 2 +-
.../shell/coresight/memcpy_thread_16k_10.sh | 2 +-
.../coresight/thread_loop_check_tid_10.sh | 2 +-
.../coresight/thread_loop_check_tid_2.sh | 2 +-
.../shell/coresight/unroll_loop_thread_10.sh | 2 +-
tools/perf/tests/shell/list.sh | 5 +-
.../tests/shell/perftool-testsuite_report.sh | 2 +-
tools/perf/tests/shell/record.sh | 2 +-
tools/perf/tests/shell/record_lbr.sh | 2 +-
tools/perf/tests/shell/record_offcpu.sh | 2 +-
tools/perf/tests/shell/stat_all_pmu.sh | 2 +-
tools/perf/tests/shell/test_arm_coresight.sh | 2 +-
.../tests/shell/test_arm_coresight_disasm.sh | 2 +-
tools/perf/tests/shell/test_arm_spe.sh | 2 +-
tools/perf/tests/shell/test_intel_pt.sh | 2 +-
.../perf/tests/shell/test_stat_intel_tpebs.sh | 2 +-
tools/perf/tests/task-exit.c | 9 +-
tools/perf/tests/tests-scripts.c | 7 +-
tools/perf/tests/tests.h | 9 +
tools/perf/util/color.h | 1 +
22 files changed, 258 insertions(+), 110 deletions(-)
--
2.47.0.rc1.288.g06298d1525-goog
next reply other threads:[~2024-10-11 22:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 22:03 Ian Rogers [this message]
2024-10-11 22:03 ` [PATCH v2 1/8] tools subcmd: Add non-waitpid check_if_command_finished() Ian Rogers
2024-10-11 22:03 ` [PATCH v2 2/8] perf test: Display number of active running tests Ian Rogers
2024-10-11 22:03 ` [PATCH v2 3/8] perf test: Reduce scope of parallel variable Ian Rogers
2024-10-11 22:03 ` [PATCH v2 4/8] perf test: Avoid list test blocking on writing to stdout Ian Rogers
2024-10-11 22:03 ` [PATCH v2 5/8] perf test: Tag parallel failing shell tests with "(exclusive)" Ian Rogers
2024-10-11 22:03 ` [PATCH v2 6/8] perf test: Add a signal handler around running a test Ian Rogers
2024-10-11 22:03 ` [PATCH v2 7/8] perf test: Run parallel tests in two passes Ian Rogers
2024-10-11 22:03 ` [PATCH v2 8/8] perf test: Make parallel testing the default Ian Rogers
2024-10-16 23:48 ` [PATCH v2 0/8] Run tests in parallel showing number of tests running Namhyung Kim
2024-10-17 0:28 ` Ian Rogers
2024-10-17 12:49 ` Ian Rogers
2024-10-17 23:28 ` Namhyung Kim
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=20241011220354.756798-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=colin.i.king@gmail.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=howardchu95@gmail.com \
--cc=iii@linux.ibm.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=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.com \
--cc=vmolnaro@redhat.com \
--cc=weilin.wang@intel.com \
/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).