From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: ab/mark-leak-free-tests-even-more (was: What's cooking in git.git (Nov 2021, #05; Fri, 19))
Date: Tue, 23 Nov 2021 14:22:16 +0100 [thread overview]
Message-ID: <211123.861r37uhls.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqa6hznvz1.fsf@gitster.g>
On Fri, Nov 19 2021, Junio C Hamano wrote:
> * ab/mark-leak-free-tests-even-more (2021-11-01) 15 commits
> - leak tests: mark some fast-import tests as passing with SANITIZE=leak
> - leak tests: mark some config tests as passing with SANITIZE=leak
> - leak tests: mark some status tests as passing with SANITIZE=leak
> - leak tests: mark some clone tests as passing with SANITIZE=leak
> - leak tests: mark some add tests as passing with SANITIZE=leak
> - leak tests: mark some diff tests as passing with SANITIZE=leak
> - leak tests: mark some apply tests as passing with SANITIZE=leak
> - leak tests: mark some notes tests as passing with SANITIZE=leak
> - leak tests: mark some update-index tests as passing with SANITIZE=leak
> - leak tests: mark some rev-parse tests as passing with SANITIZE=leak
> - leak tests: mark some rev-list tests as passing with SANITIZE=leak
> - leak tests: mark some misc tests as passing with SANITIZE=leak
> - leak tests: mark most gettext tests as passing with SANITIZE=leak
> - leak tests: mark "sort" test as passing SANITIZE=leak
> - leak tests: mark a read-tree test as passing SANITIZE=leak
>
> More tests are marked as leak-free.
>
> Will merge to 'next'?
FWIW Elijah reviewed it and acked merging it to "next" in response to
the previous What's Cooking:
https://lore.kernel.org/git/CABPp-BES7SX06i3+AZS2gxkGdbS6nHy5r00E_WhMaSpZ6PdjrA@mail.gmail.com/
I also think it's ready, and along with ab/checkout-branch-info-leakfix
(marked for 'next', yay).
Together those two form a good basis for follow-ing up and fixing some
other "big leaks". I'll be doing the big one of "struct rev_info" soon
after these land.
prev parent reply other threads:[~2021-11-23 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 7:10 What's cooking in git.git (Nov 2021, #05; Fri, 19) Junio C Hamano
2021-11-20 11:18 ` Fabian Stelzer
2021-11-20 17:30 ` Elijah Newren
2021-11-20 22:20 ` vd/sparse-reset (Was: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19)) Elijah Newren
2021-11-21 2:00 ` What's cooking in git.git (Nov 2021, #05; Fri, 19) Elijah Newren
2021-11-22 17:59 ` vd/sparse-sparsity-fix-on-read (Was: Re: What's cooking in git.git (Nov 2021, #05; Fri, 19)) Elijah Newren
2021-11-22 18:00 ` What's cooking in git.git (Nov 2021, #05; Fri, 19) Glen Choo
2021-11-22 18:05 ` Junio C Hamano
2021-11-22 22:36 ` Glen Choo
2021-11-23 13:22 ` Æ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=211123.861r37uhls.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@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 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.