On Tue Oct 22, 2024 at 21:04, Taylor Blau <me@xxxxxxxxxxxx> wrote: > On Tue, Oct 22, 2024 at 08:33:28PM +0200, Bence Ferdinandy wrote: >> >> On Tue Oct 22, 2024 at 19:39, Taylor Blau <me@xxxxxxxxxxxx> wrote: >> > On Mon, Oct 21, 2024 at 03:36:57PM +0200, Bence Ferdinandy wrote: >> >> Bence Ferdinandy (8): >> >> t/t5505-remote: set default branch to main >> >> refs: atomically record overwritten ref in update_symref >> >> remote set-head: refactor for readability >> >> remote set-head: better output for --auto >> >> refs: add TRANSACTION_CREATE_EXISTS error >> >> refs: add create_only option to refs_update_symref_extended >> >> fetch: set remote/HEAD if it does not exist >> >> fetch set_head: handle mirrored bare repositories >> > >> > After applying this topic to 'seen', I noticed some new CI breakage that >> > appears to be caused by this topic: >> > >> > https://github.com/git/git/actions/runs/11449483611/job/31855171514#step:4:2506 >> > >> > After dropping the topic locally and building with 'make SANITIZE=leak' >> > and then running t0410-partial-clone.sh, I was able to resolve the >> > failures. >> > >> > Would you mind building with 'SANITIZE=leak' and running that script to >> > see if you can address the issue? Thanks. >> >> Thanks, I can reproduce the issue. I'm hoping there are no more tricks to >> testing things :D > > Great, I'm glad that it was easily reproducible on your end. This one > should have minimal differences from the setup in CI, as I think > building with 'SANITIZE=leak' will suffice. > >> Let's see how fast I can handle this ... > > Thanks for looking. I'll send v11 to the correct thread, hopefully with no random companies in Cc :)
