From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/test-lib-tweaks (was: What's cooking in git.git (Feb 2022, #07; Fri, 25))
Date: Mon, 28 Feb 2022 15:10:54 +0100 [thread overview]
Message-ID: <220228.86tucj3wo2.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqee3q73e1.fsf@gitster.g>
On Fri, Feb 25 2022, Junio C Hamano wrote:
> * ab/test-lib-tweaks (2022-02-21) 4 commits
> - test-lib: add "fast_unwind_on_malloc=0" to LSAN_OPTIONS
> - test-lib: make $GIT_BUILD_DIR an absolute path
> - test-lib: correct commentary on TEST_DIRECTORY overriding
> - test-lib: add GIT_SAN_OPTIONS, inherit [AL]SAN_OPTIONS
>
> Random test-framework clean-up.
>
> Will merge to 'next'?
> source: <cover-v3-0.4-00000000000-20220221T155656Z-avarab@gmail.com>
I sent a very minor v4 re-roll of this which should be ready for "next",
i.e. it addresses comments (including yours) on the v3:
https://lore.kernel.org/git/cover-v4-0.4-00000000000-20220227T102256Z-avarab@gmail.com/
If you're considering branch name/log message changes before merging (it
would be fine without) I'd suggest:
ab/test-lib-leak-diagnostics
Spend more CPU to emit meaningful stack traces when testing under
SANITIZE=leak, and allow overriding ASAN and LSAN options from the
environment without breaking our tests in cases where they relied on
setting their own options.
prev parent reply other threads:[~2022-02-28 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 2:44 What's cooking in git.git (Feb 2022, #07; Fri, 25) Junio C Hamano
2022-02-26 8:54 ` en/merge-tree (Was: Re: What's cooking in git.git (Feb 2022, #07; Fri, 25)) Elijah Newren
2022-02-26 9:11 ` en/present-despite-skipped " Elijah Newren
2022-03-07 16:15 ` Johannes Schindelin
2022-02-28 12:38 ` What's cooking in git.git (Feb 2022, #07; Fri, 25) Tao Klerks
2022-02-28 13:42 ` Ævar Arnfjörð Bjarmason
2022-03-01 11:56 ` Tao Klerks
2022-03-01 18:06 ` Junio C Hamano
2022-03-01 19:25 ` Tao Klerks
2022-02-28 13:56 ` ds/commit-graph-gen-v2-fixes (was Re: What's cooking in git.git (Feb 2022, #07; Fri, 25)) Derrick Stolee
2022-02-28 14:10 ` Ævar Arnfjörð Bjarmason [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=220228.86tucj3wo2.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).