linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Brnak <jbrnak@redhat.com>
To: Ian Rogers <irogers@google.com>
Cc: namhyung@kernel.org, acme@kernel.org, acme@redhat.com,
	linux-perf-users@vger.kernel.org, mpetlan@redhat.com,
	vmolnaro@redhat.com
Subject: Re: [PATCH v4 5/7] perf test: Introduce storing logs for shell tests
Date: Wed, 12 Nov 2025 13:44:31 +0100	[thread overview]
Message-ID: <aRR788vna0u-CEUU@jbrnak-thinkpadx1carbongen9.tpbc.csb> (raw)
In-Reply-To: <CAP-5=fUJZEoAbNu+ZzjgshHRbq94dLn6-KPdzC=i9i350K=4dw@mail.gmail.com>

On Tue, Sep 30, 2025 at 12:00:19PM -0700, Ian Rogers wrote:
> On Tue, Sep 30, 2025 at 9:09 AM Jakub Brnak <jbrnak@redhat.com> wrote:
> >
> > From: Veronika Molnarova <vmolnaro@redhat.com>
> >
> > Create temporary directories for storing log files for shell tests
> > that could help while debugging. The log files are necessary for
> > perftool testsuite test cases also. If the variable PERFTEST_KEEP_LOGS
> > is set keep the logs, else delete them.
> 
> I think log files for tests are a good idea. We run tests in parallel
> but read the stdout/stderr sequentially. For a failing test we may
> fail to read stdout/stderr in some situations as the process has long
> since died. Rather than add log files specifically for shell tests
> perhaps update start_test to pass the file descriptors to the child
> test processes and then clean up in finish_test?
> https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/tree/tools/perf/tests/builtin-test.c?h=perf-tools-next#n528
> 
> Thanks,
> Ian

Hi Ian, 

Thanks for the feedback.

You've raised a good point about capturing stdout/stderr for parallel runs,
but this patch is solving a different problem.

The logs we're storing here are test-generated data artifacts, not the
stdout/stderr of the test process itself.

Our patch provides a $PERFSUITE_RUN_DIR environment variable so that commands inside the shell script (e.g., perf record)
have a known directory to save these files for debugging.

Thanks,
Jakub


  reply	other threads:[~2025-11-12 12:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 16:09 [PATCH v4 0/7] Introduce structure for shell tests Jakub Brnak
2025-09-30 16:09 ` [PATCH v4 1/7] perf test perftool_testsuite: Use absolute paths Jakub Brnak
2025-09-30 18:28   ` Ian Rogers
2025-10-01 12:37     ` Arnaldo Carvalho de Melo
2025-09-30 16:09 ` [PATCH v4 2/7] perf tests: Create a structure for shell tests Jakub Brnak
2025-09-30 18:49   ` Ian Rogers
2025-10-14 13:26     ` Jakub Brnak
2025-09-30 16:09 ` [PATCH v4 3/7] perf test: Provide setup for the shell test suite Jakub Brnak
2025-09-30 18:51   ` Ian Rogers
2025-09-30 16:09 ` [PATCH v4 4/7] perftool-testsuite: Add empty setup for base_probe Jakub Brnak
2025-09-30 18:52   ` Ian Rogers
2025-09-30 16:09 ` [PATCH v4 5/7] perf test: Introduce storing logs for shell tests Jakub Brnak
2025-09-30 19:00   ` Ian Rogers
2025-11-12 12:44     ` Jakub Brnak [this message]
2025-11-12 16:37       ` Ian Rogers
2025-11-13 15:11         ` Jakub Brnak
2025-09-30 16:09 ` [PATCH v4 6/7] perf test: Format log directories " Jakub Brnak
2025-09-30 16:09 ` [PATCH v4 7/7] perf test: Remove perftool drivers Jakub Brnak

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=aRR788vna0u-CEUU@jbrnak-thinkpadx1carbongen9.tpbc.csb \
    --to=jbrnak@redhat.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=vmolnaro@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 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).