public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org,
	 Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ci(*-leaks): skip the git-svn tests to save time
Date: Mon, 26 Jan 2026 08:06:03 -0800	[thread overview]
Message-ID: <xmqqikcojr4k.fsf@gitster.g> (raw)
In-Reply-To: <82b656a5-e5c8-4056-8ec5-4bdab9ef7128@gmail.com> (Phillip Wood's message of "Mon, 26 Jan 2026 09:47:46 +0000")

Phillip Wood <phillip.wood123@gmail.com> writes:

> I think that unless the libsvn that linked against was built with 
> -fsanitize=leak we wouldn't find any leaks in it anyway. When I wrote my 
> original mail I was imagining C implementation that forked "svn" but 
> replaced the perl code with C that called the appropriate functions in 
> libgit rather than forking git.

It was the scenario I was assuming as well, but I simply forgot to
consider that we want to catch leaks in our "client" code (client
from the point of view of the libsvn library).

And you are right.  It can be done to check our leaks without being
able to touch libsvn to fix their leaks, even though we may have to
filter out noises from the leak checker if there are their leaks we
cannot plug.

> In that case I think there's an argument 
> for checking that our code does not leak. Anyway this is all rather 
> hypothetical as we're not likely to rewrite these scripts in C.

;-).

      reply	other threads:[~2026-01-26 16:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 17:31 [PATCH] ci(*-leaks): skip the git-svn tests to save time Johannes Schindelin via GitGitGadget
2026-01-16 19:20 ` Junio C Hamano
2026-01-17 15:04 ` Phillip Wood
2026-01-17 18:34   ` Junio C Hamano
2026-01-17 19:02     ` Kristoffer Haugsbakk
2026-01-18  0:35       ` Junio C Hamano
2026-01-20 10:31         ` Phillip Wood
2026-01-20 10:34     ` Phillip Wood
2026-01-20 15:42       ` Junio C Hamano
2026-01-23 14:47         ` Phillip Wood
2026-01-23 17:46           ` Junio C Hamano
2026-01-26  9:47             ` Phillip Wood
2026-01-26 16:06               ` Junio C Hamano [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=xmqqikcojr4k.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=phillip.wood123@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