From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/mark-leak-free-tests-even-more (was: What's cooking in git.git (Nov 2021, #04; Sun, 14))
Date: Mon, 15 Nov 2021 20:30:46 +0100 [thread overview]
Message-ID: <211115.861r3hrz61.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqv90tfhh2.fsf@gitster.g>
On Mon, Nov 15 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'?
That would be great. I've got a rather large queue of leak fixes
pending, and due to marking up the tests incrementally they've pretty
much got to go in sequence.
For this sort of topic that's just marking existing tests as running
under the linux-leaks job I'd think it could proceed relatively quickly
after it's not been causing test smoke on master/next/seen for a bit,
which with the release cycle has been a couple of weeks in this case.
next prev parent reply other threads:[~2021-11-15 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 17:37 What's cooking in git.git (Nov 2021, #04; Sun, 14) Junio C Hamano
2021-11-15 19:30 ` Ævar Arnfjörð Bjarmason [this message]
2021-11-15 22:16 ` ab/mark-leak-free-tests-even-more (was: What's cooking in git.git (Nov 2021, #04; Sun, 14)) Elijah Newren
2021-11-15 19:35 ` ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
2021-11-15 19:37 ` ab/refs-errno-cleanup + hn/reftable " Ævar Arnfjörð Bjarmason
2021-11-15 20:00 ` What's cooking in git.git (Nov 2021, #04; Sun, 14) Fabian Stelzer
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=211115.861r3hrz61.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).