From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Aditya Gupta <adityag@linux.ibm.com>
Cc: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
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>,
Kan Liang <kan.liang@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1] perf test: Avoid python leak sanitizer test failures
Date: Tue, 23 Jul 2024 15:33:57 -0300 [thread overview]
Message-ID: <Zp_3lQ1fZDn2Qxy2@x1> (raw)
In-Reply-To: <6645190c-e66f-49db-a23d-e08f6308a422@linux.ibm.com>
On Thu, Jul 18, 2024 at 02:17:58PM +0530, Aditya Gupta wrote:
> On 17/07/24 22:27, Ian Rogers wrote:
> > +# Disable lsan to avoid warnings about python memory leaks.
> > +export ASAN_OPTIONS=detect_leaks=0
> > +
> > cleanup() {
> > rm -f perf.data
> > rm -f perf.data.old
> Looks good, and test passes with this patch:
> Reviewed-by: Aditya Gupta <adityag@linux.ibm.com>
Thanks, applied to tmp.perf-tools-next,
- Arnaldo
>
> Linux-ci build test results: https://github.com/adi-g15-ibm/linux-ci/actions?query=branch%3Atmp-test-branch-25073
prev parent reply other threads:[~2024-07-23 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 16:57 [PATCH v1] perf test: Avoid python leak sanitizer test failures Ian Rogers
2024-07-18 8:47 ` Aditya Gupta
2024-07-23 18:33 ` Arnaldo Carvalho de Melo [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=Zp_3lQ1fZDn2Qxy2@x1 \
--to=acme@kernel.org \
--cc=adityag@linux.ibm.com \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--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=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.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).