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

Re: [ANNOUNCE] Git v2.48.0-rc0

From
Patrick Steinhardt <ps@pks.im>
Date
Dec 20, 2024, 07:08 UTC
Message-ID
<Z2UX2v8sc-DELaVm@pks.im>
In-Reply-To
<00ca01db5257$12708d00$3751a700$@nexbridge.com>
On Thu, Dec 19, 2024 at 03:46:20PM -0500, rsbecker@nexbridge.com wrote:
Show 12 quoted lines
> On December 18, 2024 11:07 AM, I wrote:
> >All tests, actually.
> >
> >$ GIT_TEST_DEFAULT_REF_FORMAT=reftable GIT_TEST_CLONE_2GB=true sh t0000-
> >basic.sh --verbose -i -x
> >error: reftable: transaction prepare: out of memory
> >error: cannot run git init
> 
> Any updates or hypothesis on this? Our test system has loads of memory
> - I cannot figure out where the allocation failure takes place. There
> is a limit to how much memory can be allocated, but it is very high
> and our virtual memory is extensive, but this is a 32-bit build.

My hypothesis is that this is caused by ps/reftable-alloc-failures, but I am unable to tell where exactly the error comes from. So I'm dependent on your input.

Could you please bisect the error? Finding out where the error is raised would also be quite helpful. It has to be one of the reftable functions that returns REFTABLE_OUT_OF_MEMORY_ERROR, but other than that I do not have any more gut feeling right now.

Patrick
Previous: rsbecker@nexbridge.comNext: rsbecker@nexbridge.com
Message 11 of 16 in “[ANNOUNCE] Git v2.48.0-rc0”
  1. Junio C HamanoDec 16, 2024
  2. rsbecker@nexbridge.comDec 17, 2024
  3. Patrick SteinhardtDec 17, 2024
  4. rsbecker@nexbridge.comDec 17, 2024
  5. Patrick SteinhardtDec 17, 2024
  6. rsbecker@nexbridge.comDec 17, 2024
  7. rsbecker@nexbridge.comDec 17, 2024
  8. Patrick SteinhardtDec 18, 2024
  9. rsbecker@nexbridge.comDec 18, 2024
  10. rsbecker@nexbridge.comDec 19, 2024
  11. Patrick SteinhardtDec 20, 2024
  12. rsbecker@nexbridge.comDec 20, 2024
  13. Patrick SteinhardtDec 20, 2024
  14. rsbecker@nexbridge.comDec 20, 2024
  15. Patrick SteinhardtDec 21, 2024
  16. rsbecker@nexbridge.comDec 21, 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.