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

RE: [ANNOUNCE] Git v2.48.0-rc0

From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date
Dec 19, 2024, 20:46 UTC
Message-ID
<00ca01db5257$12708d00$3751a700$@nexbridge.com>
In-Reply-To
<Z2JyFB3CddYM_LP4@pks.im>
On December 18, 2024 11:07 AM, I wrote:
Show 57 quoted lines
>On December 18, 2024 1:57 AM, Patrick Steinhardt wrote:
>>On Tue, Dec 17, 2024 at 02:00:01PM -0500, rsbecker@nexbridge.com wrote:
>>> On December 17, 2024 8:48 AM, I wrote:
>>> >This is on the latest OS version of NonStop x86. The test is done
>>> >via the
>>> >following:
>>> >With OpenSSL 3.4 The T0625 is Expat.
>>> >
>>> >When run as follows:
>>> >GIT_TEST_DEFAULT_REF_FORMAT=reftable GIT_TEST_CLONE_2GB=true
>>> >/usr/coreutils/bin/make -k test V=1 CFLAGS="-g -O2 -Winline
>>> >-I/usr/local- ssl3.4/include -I/usr/coreutils/include
>>> -I/usr/tandem/xml/T0625L01_AAE/include"
>>> >LDFLAGS="/usr/coreutils/lib/libz.a
>>> >-L/usr/local-ssl3.4/lib -L/usr/coreutils/lib
>>> -L/usr/tandem/xml/T0625L01_AAE/lib"
>>> >TEST_LINT= SHELL=/usr/coreutils/bin/bash
>>> >
>>> >The results are:
>>> >*** t0000-basic.sh ***
>>> >error: cannot run git init
>>> >Makefile:77: recipe for target 't0000-basic.sh' failed
>>> >make[2]: *** [t0000-basic.sh] Error 1
>>> >*** t0001-init.sh ***
>>> >error: cannot run git init
>>> >Makefile:77: recipe for target 't0001-init.sh' failed
>>> >make[2]: *** [t0001-init.sh] Error 1
>>> >*** t0002-gitfile.sh ***
>>> >error: cannot run git init
>>> >Makefile:77: recipe for target 't0002-gitfile.sh' failed
>>> >make[2]: *** [t0002-gitfile.sh] Error 1 etc for all tests.
>>> >
>>> >Removing GIT_TEST_DEFAULT_REF_FORMAT=reftable allows the whole test
>>> >suite
>>> to
>>> >pass.
>>> >
>>> >There are environment size limits (about 32Kb) in bash on the box,
>>> >so it is
>>> possible a
>>> >boundary was crossed internal to the test setup.
>>>
>>> I did find this, in t0000-basic:
>>> not ok 69 - init with GIT_DEFAULT_REF_FORMAT=reftable
>>
>>You mean t0001-init.sh, right?
>>
>>> but have no more details. When should I break in gdb to get a backtrace?
>>
>>Can you please run that test with "-ix" and post the logs?
>
>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.

--Randall
Previous: rsbecker@nexbridge.comNext: Patrick Steinhardt
Message 10 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.