From: Josh Steadmon <steadmon@google.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
stolee@gmail.com
Subject: Re: [PATCH] t/lib-httpd: pass LSAN_OPTIONS through apache
Date: Tue, 7 May 2019 15:45:20 -0700 [thread overview]
Message-ID: <20190507224520.GD26779@google.com> (raw)
In-Reply-To: <20190507223046.GA16315@sigill.intra.peff.net>
On 2019.05.07 18:30, Jeff King wrote:
> Just as we instruct Apache to pass through ASAN_OPTIONS (so that
> server-side Git programs it spawns will respect our options while
> running the tests), we should do the same with LSAN_OPTIONS. Otherwise
> trying to collect a list of leaks like:
>
> export LSAN_OPTIONS=exitcode=0:log_path=/tmp/lsan
> make SANITIZE=leak test
>
> won't work for http tests (the server-side programs won't log their
> leaks to the right place, and they'll prematurely die, producing a
> spurious test failure).
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> Found this after giving similar advice in
>
> https://public-inbox.org/git/20190507222601.GA976@sigill.intra.peff.net/
>
> t/lib-httpd/apache.conf | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/t/lib-httpd/apache.conf b/t/lib-httpd/apache.conf
> index 06a81b54c7..5c1c86c193 100644
> --- a/t/lib-httpd/apache.conf
> +++ b/t/lib-httpd/apache.conf
> @@ -76,6 +76,7 @@ PassEnv GIT_VALGRIND
> PassEnv GIT_VALGRIND_OPTIONS
> PassEnv GNUPGHOME
> PassEnv ASAN_OPTIONS
> +PassEnv LSAN_OPTIONS
> PassEnv GIT_TRACE
> PassEnv GIT_CONFIG_NOSYSTEM
> PassEnv GIT_TEST_SIDEBAND_ALL
> --
> 2.21.0.1314.g224b191707
Looks good to me.
prev parent reply other threads:[~2019-05-07 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 22:30 [PATCH] t/lib-httpd: pass LSAN_OPTIONS through apache Jeff King
2019-05-07 22:45 ` Josh Steadmon [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=20190507224520.GD26779@google.com \
--to=steadmon@google.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=stolee@gmail.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).