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

Re: What's cooking in git.git (Jan 2025, #05; Fri, 17)

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 22, 2025, 17:38 UTC
Message-ID
<xmqqa5biyciu.fsf@gitster.g>
In-Reply-To
<CAOLa=ZT4nws0irdZKUuWc70Rv9RUNQuSXnGAt1SnE1O+umSReg@mail.gmail.com>
Karthik Nayak <karthik.188@gmail.com> writes:
Show 41 quoted lines
> Karthik Nayak <karthik.188@gmail.com> writes:
>
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> * kn/reflog-migration-fix (2025-01-15) 1 commit
>>>   (merged to 'next' on 2025-01-16 at ae8f9ce9a0)
>>>  + reftable: write correct max_update_index to header
>>>  (this branch is used by kn/reflog-migration-fix-followup.)
>>>
>>>  "git refs migrate" for migrating reflog data was broken.
>>>
>>>  Will merge to 'master'.
>>>  cf. <Z4mUizLNUdq_1BgY@tapette.crustytoothpaste.net>
>>>  source: <CAOLa=ZTL9n_DPhNr49XAd6bT838kc09oVx_AH7Pb4o8VK_xQ9w@mail.gmail.com>
>>
>> This seems to be breaking on 'next'. I tested it locally with
>>
>>   GIT_TEST_DEFAULT_REF_FORMAT=reftable meson test -v --test-args='-i' t1400-update-ref
>>
>> my local tests were made on files backend, and it didn't trigger on the
>> CI either for some reason (I shall investigate that soon). But dscho
>> (CC'd) reported that macos builds for reftable were failing [1] for his
>> branch and I could bisect it to this.
>>
>> I'm yet to understand why this fails and also why the CI didn't notify
>> of the issue. But that is something I shall do next. For now we need to
>> remove it from next.
>>
>> [1]: https://github.com/dscho/git/actions/runs/12906424058/job/35987723223
>
> This is reproducible when the leak sanitizier is enabled and tested
> against reftable:
>
> So setting up meson with:
>   CC=clang meson setup --reconfigure -Db_sanitize=address,undefined build
> and running the test in the build folder with:
>   GIT_TEST_DEFAULT_REF_FORMAT=reftable meson test -v
> --test-args='-ixd' t1400-update-ref
>
> reproduces the issue. I haven't found the root cause yet, but will
> mostly call it a day and get back to this tomorrow.
Thanks.  I'll mark the topic as on-hold.
Previous: Karthik NayakNext: Junio C Hamano
Message 18 of 23 in “What's cooking in git.git (Jan 2025, #05; Fri, 17)”
  1. Junio C HamanoJan 18, 2025
  2. Jeff KingJan 18, 2025
  3. Junio C HamanoJan 18, 2025
  4. Jeff KingJan 19, 2025
  5. Jeff KingJan 19, 2025
  6. Junio C HamanoJan 21, 2025
  7. David AguilarJan 20, 2025
  8. help: make help.autocorrect = 1 the same as "prompt"David Aguilar, Jan 20, 2025
  9. Junio C HamanoJan 21, 2025
  10. Derrick StoleeJan 21, 2025
  11. Junio C HamanoJan 21, 2025
  12. Taylor BlauJan 22, 2025
  13. Junio C HamanoJan 22, 2025
  14. Taylor BlauJan 23, 2025
  15. Junio C HamanoJan 23, 2025
  16. Karthik NayakJan 22, 2025
  17. Karthik NayakJan 22, 2025
  18. Junio C HamanoJan 22, 2025
  19. Junio C HamanoJan 23, 2025
  20. Patrick SteinhardtJan 23, 2025
  21. Junio C HamanoJan 23, 2025
  22. Karthik NayakJan 24, 2025
  23. Junio C HamanoJan 24, 2025

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.