From: <rsbecker@nexbridge.com>
To: "'Patrick Steinhardt'" <ps@pks.im>
Cc: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.48.0-rc0
Date: Thu, 19 Dec 2024 15:46:20 -0500 [thread overview]
Message-ID: <00ca01db5257$12708d00$3751a700$@nexbridge.com> (raw)
In-Reply-To:
On December 18, 2024 11:07 AM, I wrote:
>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
next prev parent reply other threads:[~2024-12-19 20:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 18:14 [ANNOUNCE] Git v2.48.0-rc0 Junio C Hamano
2024-12-17 0:07 ` rsbecker
2024-12-17 4:51 ` Patrick Steinhardt
2024-12-17 13:47 ` rsbecker
2024-12-17 14:24 ` Patrick Steinhardt
2024-12-17 16:18 ` rsbecker
2024-12-17 19:00 ` rsbecker
2024-12-18 6:56 ` Patrick Steinhardt
2024-12-18 16:07 ` rsbecker
2024-12-19 20:46 ` rsbecker [this message]
2024-12-20 7:08 ` Patrick Steinhardt
2024-12-20 19:23 ` rsbecker
2024-12-20 19:37 ` Patrick Steinhardt
2024-12-20 21:21 ` rsbecker
2024-12-21 11:50 ` Patrick Steinhardt
2024-12-21 15:11 ` rsbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00ca01db5257$12708d00$3751a700$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.