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

Re: [PATCH 1/4] t0080: mark as leak-free

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 30, 2024, 20:00 UTC
Message-ID
<xmqqr0hya8x3.fsf@gitster.g>
In-Reply-To
<20240130055333.GB166761@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Setting the flag now just makes sure we continue correctly on that path,
> rather than getting surprised near the end of the road that t-basic has
> some dumb leak. Plus it avoids the script popping up as a false positive
> when checking for scripts which can be marked.

Alright. Any such "dumb leak" in the "basic" would hopefully be caught by the real t-$other unit tests exercised under the leak sanitizer, I hope, but it is not worth our time wondering if it makes sense to special case t0080 specifically.

Previous: Jeff KingNext: Rubén Justo
Message 8 of 14 in “mark tests as leak-free”
  1. 0/4 mark tests as leak-freeRubén Justo, Jan 29, 2024
  2. 1/4 t0080: mark as leak-freeRubén Justo, Jan 29, 2024
  3. Junio C HamanoJan 29, 2024
  4. Rubén JustoJan 29, 2024
  5. Junio C HamanoJan 29, 2024
  6. Rubén JustoJan 30, 2024
  7. Jeff KingJan 30, 2024
  8. Junio C HamanoJan 30, 2024
  9. 2/4 t5332: mark as leak-freeRubén Justo, Jan 29, 2024
  10. 3/4 t6113: mark as leak-freeRubén Justo, Jan 29, 2024
  11. 4/4 test-lib: check for TEST_PASSES_SANITIZE_LEAKRubén Justo, Jan 29, 2024
  12. Junio C HamanoJan 29, 2024
  13. Jeff KingJan 30, 2024
  14. Junio C HamanoJan 30, 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.