From: Namhyung Kim <namhyung@kernel.org>
To: Jakub Brnak <jbrnak@redhat.com>
Cc: acme@kernel.org, acme@redhat.com,
linux-perf-users@vger.kernel.org, irogers@google.com,
mpetlan@redhat.com
Subject: Re: [PATCH v6 0/7] Introduce structure for shell tests
Date: Thu, 12 Mar 2026 11:26:09 -0700 [thread overview]
Message-ID: <abMFQbTSW5jwpAa2@google.com> (raw)
In-Reply-To: <20260309155728.98026-1-jbrnak@redhat.com>
Hello,
On Mon, Mar 09, 2026 at 04:57:21PM +0100, Jakub Brnak wrote:
> Hi,
>
> Sending the next revision of patches for perftool-testsuite structure
> setup which incorporates the changes in Patch 4 suggested by Ian.
Can you please add a documentation for the directory structure, setup,
log and other details?
Thanks,
Namhyung
>
> Thanks,
> Jakub
>
> Link to v5: https://lore.kernel.org/linux-perf-users/20251125155648.197527-1-jbrnak@redhat.com/
>
> Changes since v5:
> Patch 4: fixed log deletion logic to ensure logs are only removed after
> all tests (including those executed in parallel) have fully completed
>
> Jakub Brnak (7):
> perf tests: Create a structure for shell tests
> perf test: Provide setup for the shell test suite
> perftool-testsuite: Add empty setup for base_probe
> perf test: Introduce storing logs for shell tests
> perf test: Format log directories for shell tests
> perf test: Remove perftool drivers
> perf test: Fix relative path for 'stderr-whitelist.txt'
>
> tools/perf/tests/builtin-test.c | 141 ++++++++-
> tools/perf/tests/shell/base_probe/setup.sh | 13 +
> .../tests/shell/base_report/test_basic.sh | 6 +-
> .../tests/shell/perftool-testsuite_probe.sh | 24 --
> .../tests/shell/perftool-testsuite_report.sh | 23 --
> tools/perf/tests/tests-scripts.c | 289 +++++++++++++++---
> tools/perf/tests/tests-scripts.h | 17 ++
> tools/perf/tests/tests.h | 8 +-
> 8 files changed, 413 insertions(+), 108 deletions(-)
> create mode 100755 tools/perf/tests/shell/base_probe/setup.sh
> delete mode 100755 tools/perf/tests/shell/perftool-testsuite_probe.sh
> delete mode 100755 tools/perf/tests/shell/perftool-testsuite_report.sh
>
> --
> 2.52.0
>
prev parent reply other threads:[~2026-03-12 18:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 15:57 [PATCH v6 0/7] Introduce structure for shell tests Jakub Brnak
2026-03-09 15:57 ` [PATCH v6 1/7] perf tests: Create a " Jakub Brnak
2026-03-10 15:05 ` Ian Rogers
2026-03-09 15:57 ` [PATCH v6 2/7] perf test: Provide setup for the shell test suite Jakub Brnak
2026-03-10 15:14 ` Ian Rogers
2026-03-09 15:57 ` [PATCH v6 3/7] perftool-testsuite: Add empty setup for base_probe Jakub Brnak
2026-03-09 15:57 ` [PATCH v6 4/7] perf test: Introduce storing logs for shell tests Jakub Brnak
2026-03-10 15:22 ` Ian Rogers
2026-03-09 15:57 ` [PATCH v6 5/7] perf test: Format log directories " Jakub Brnak
2026-03-10 15:24 ` Ian Rogers
2026-03-09 15:57 ` [PATCH v6 6/7] perf test: Remove perftool drivers Jakub Brnak
2026-03-09 15:57 ` [PATCH v6 7/7] perf test: Fix relative path for 'stderr-whitelist.txt' Jakub Brnak
2026-03-12 18:26 ` 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=abMFQbTSW5jwpAa2@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=jbrnak@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.