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

Re: [PATCH 00/10] leak tests: mark more tests as passing

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Oct 12, 2021, 13:40 UTC
Message-ID
<87czoajr35.fsf@evledraar.gmail.com>
In-Reply-To
<CABPp-BEpCa7dxYqe2R82N_eVzx5e17C2w+d1zD9XWzyEXCDbPw@mail.gmail.com>
On Wed, Oct 06 2021, Elijah Newren wrote:
Show 21 quoted lines
> On Wed, Oct 6, 2021 at 2:50 AM Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>>
>> This goes on top of ab/sanitize-leak-ci, in that topic I introduced a
>> "linux-leaks" job that runs in CI and checks that we don't have
>> SANITIZE=leak regressions, but it just marked one test file as passing
>> under that mode.
>>
>> That was out of an abundance of caution, and to not conflate any
>> potential failures with the mode itself.
>>
>> This series marks up a lot of tests as passing, ensuring that they
>> won't regress when it comes to memory leaks.
>
> I like the series.  It does have the potential to annoy folks who want
> to add additional tests which make use of git commands outside the
> area they are modifying and which happen to have pre-existing leaks.
> But, I think in such cases, they could just remove the
> TEST_PASSES_SANITIZE_LEAK=true and mention it in their commit message.
> And when the checks fail because of a git command someone is
> modifying, then we get useful early signal and the author can address
> the problem.

Yes there's a definite chance for annoyance while the common leak fixes I've got planned are cooking, i.e. as we've discussed elsewhere "git log" and "git checkout" among others leak in almost any invocation you cank think of, so if you add a new test that steps on those landmines (including via test_commit!) you'll run afoul of this.

But I'm hoping to have those common cases sorted out SOON, so hopefully any problems with this are short lived.

Just FWIW if this does happen you probably won't and shouldn't need to remove the TEST_PASSES_SANITIZE_LEAK=true entirely, it should be enough to make the specific test use "!SANITIZE_LEAK" as a prerequisite. See 956d2e4639b (tests: add a test mode for SANITIZE=leak, run it in CI, 2021-09-23).

Well, that can also get annoying if e.g. you want to add a "test_commit" to a short test that has an existing setup (you'd need to split up the "setup" phase).

Anyway, will re-roll, just FYI^
 
Previous: Junio C HamanoNext: Ævar Arnfjörð Bjarmason
Message 17 of 27 in “leak tests: mark more tests as passing”
  1. 00/10 leak tests: mark more tests as passingÆvar Arnfjörð Bjarmason, Oct 6, 2021
  2. 01/10 leak tests: run various built-in tests in t00*.sh SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  3. Junio C HamanoOct 7, 2021
  4. 02/10 leak tests: run various "test-tool" tests in t00*.sh SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  5. 03/10 leak tests: mark t0000-init.sh as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  6. Junio C HamanoOct 7, 2021
  7. Ævar Arnfjörð BjarmasonOct 12, 2021
  8. 04/10 leak tests: mark all ls-tree tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  9. 05/10 leak tests: mark all trace2 tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  10. 07/10 leak tests: mark some ls-files tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  11. 06/10 leak tests: mark all checkout-index tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  12. 09/10 leak tests: mark various "generic" tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  13. 08/10 leak tests: mark some read-tree tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  14. 10/10 leak tests: mark some misc tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 6, 2021
  15. Elijah NewrenOct 6, 2021
  16. Junio C HamanoOct 7, 2021
  17. Ævar Arnfjörð BjarmasonOct 12, 2021
  18. 0/9 leak tests: mark more tests as passingÆvar Arnfjörð Bjarmason, Oct 12, 2021
  19. 1/9 leak tests: run various built-in tests in t00*.sh SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021
  20. 2/9 leak tests: run various "test-tool" tests in t00*.sh SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021
  21. 3/9 leak tests: mark all ls-tree tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021
  22. 4/9 leak tests: mark all trace2 tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021
  23. 5/9 leak tests: mark all checkout-index tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021
  24. 6/9 leak tests: mark some ls-files tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021
  25. 7/9 leak tests: mark some read-tree tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021
  26. 8/9 leak tests: mark various "generic" tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021
  27. 9/9 leak tests: mark some misc tests as passing with SANITIZE=leakÆvar Arnfjörð Bjarmason, Oct 12, 2021

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.