Re: [Savannah-hackers-public] Out of memory issues on Savannah?

[Simon Josefsson]

Hi

Not really a solution to the savannah malloc failures (I've been seeing
them too when pulling gnulib 10x in parallel from savannah during
continous integration pipeline jobs) but a note that I am (as
libidn/libidn2 maintainer) considering to not use a gnulib submodule but
rather rely on ./bootstrap to pull in gnulib through some other
mechanism, which would allow you to use a gnulib mirror and the
--gnulib-srcdir or --gnulib-refdir options to ./bootstrap, which would
reduce savannah gnulib clone usage.

Are there any savannah usage graphs per-project?  I wonder if gnulib is
a top consumer of resources, or if some other project (guix?) is a large
consumer that needs optimizing.

/Simon

"Phong X. Nguyen" via "Discussions among Savannah Hackers, open
subscription" <savannah-hackers-public@gnu.org> writes:

> Hello,
>
> We pull down libidn and libidn2, both of which rely on gnulib and we have
> with some increasing frequency seen remote out of memory errors. I saw from
> the prior issues other people have had that we should contact this mailing
> list if we need some assistance:
>
> remote: fatal: Out of memory, malloc failed (tried to allocate 49091 bytes)
>
> remote: aborting due to possible repository corruption on the remote side.
> fatal: protocol error: bad pack header
> Clone of 'https://git.savannah.gnu.org/git/gnulib.git' into submodule path
> 'gnulib' failed
>
> Thanks,
> - Phong X. Nguyen
>

signature.asc
Description: PGP signature