git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Re* [PATCH] t0613: mark as leak-free

From
Patrick Steinhardt <ps@pks.im>
Date
Jul 24, 2024, 05:16 UTC
Message-ID
<ZqCOEGfTdOSAL60w@tanuki>
In-Reply-To
<4b1391d5-89c2-41b1-b1de-e1bd26b9f10e@gmail.com>
On Wed, Jul 24, 2024 at 01:07:23AM +0200, Rubén Justo wrote:
Show 15 quoted lines
> On Tue, Jul 23, 2024 at 05:03:39PM -0400, Jeff King wrote:
> > On Mon, Jul 22, 2024 at 11:02:24AM +0200, Patrick Steinhardt wrote:
> > So I dunno. If we think people are paying attention to CI on their
> > topics, and we think that we are close enough to leak-free that (1b)
> > won't come up a lot, it might make sense. I'm not quite sure we're there
> > yet on the latter, but it's mostly gut feeling (and I know things have
> > gotten a bit better recently, too).
> 
> I don't know either.  Maybe it seems a bit early still considering the
> numbers we have: 
> 
>    $ git grep -l PASSES_SANITIZE_LEAK=true t/t[0-9][0-9][0-9][0-9]-*.sh | wc -l
>    678
>    $ git grep -L PASSES_SANITIZE_LEAK=true t/t[0-9][0-9][0-9][0-9]-*.sh | wc -l
>    329

These numbers aren't quite right -- you have to filter out most of the tests that include "lib-git-svn.sh", which reverses the schema and makes leak checks opt-out (?!). That brings me to the following hacky numbers:

    $ grep -l TEST_PASSES_SANITIZE_LEAK=true t[0-9][0-9][0-9][0-9]-*.sh | grep -v svn | wc -l
    678
    $ grep -L TEST_PASSES_SANITIZE_LEAK=true t[0-9][0-9][0-9][0-9]-*.sh | grep -v svn | wc -l
    261

I've got two local topic branches pending that reduce the number of failing tests even further. One is the Perforce series I've sent out yesterday. And then another random set of leak fixes. Which together bring us to:

    $ grep -l TEST_PASSES_SANITIZE_LEAK=true t[0-9][0-9][0-9][0-9]-*.sh | grep -v svn | wc -l
    749
    $ grep -L TEST_PASSES_SANITIZE_LEAK=true t[0-9][0-9][0-9][0-9]-*.sh | grep -v svn | wc -l
    190

So considering that it's currently still rather easy to make progress, I'd vote for keeping things as-is and wait for another couple of series to land before switching to opt-out.

Patrick
Previous: Rubén JustoNext: Rubén Justo
Message 10 of 11 in “t0613: mark as leak-free”
  1. t0613: mark as leak-freeRubén Justo, Jun 30, 2024
  2. Jeff KingJul 1, 2024
  3. Rubén JustoJul 1, 2024
  4. t0612: mark as leak-freeRubén Justo, Jul 1, 2024
  5. Eric SunshineJul 1, 2024
  6. t0612: mark as leak-freeRubén Justo, Jul 1, 2024
  7. Patrick SteinhardtJul 22, 2024
  8. Jeff KingJul 23, 2024
  9. Re* [PATCH] t0613: mark as leak-freeRubén Justo, Jul 23, 2024
  10. Patrick SteinhardtJul 24, 2024
  11. Rubén JustoJul 24, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.