On Mon, Nov 15, 2021 at 12:35 PM Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote: > > 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. I just gave it my belated review; I think it's helpful and also pretty simple. Merging to next seems like a good plan to me.
