git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: rsbecker@nexbridge.com
Cc: 'Junio C Hamano' <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.48.0-rc0
Date: Fri, 20 Dec 2024 08:08:10 +0100	[thread overview]
Message-ID: <Z2UX2v8sc-DELaVm@pks.im> (raw)
In-Reply-To: <00ca01db5257$12708d00$3751a700$@nexbridge.com>

On Thu, Dec 19, 2024 at 03:46:20PM -0500, rsbecker@nexbridge.com wrote:
> 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

  reply	other threads:[~2024-12-20  7:08 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
2024-12-20  7:08             ` Patrick Steinhardt [this message]
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=Z2UX2v8sc-DELaVm@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rsbecker@nexbridge.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).