On 2022-03-17, Maxim Cournoyer wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
>> Vagrant Cascadian <vagrant@debian.org> skribis:
>>> On 2021-05-02, Vagrant Cascadian wrote:
>>>> On 2021-05-02, Ludovic Courtès wrote:
>>>>> Guile 3.0’s compiler with ‘-O1’ (which is what we use for package files)
>>>>> uses much less memory than 2.2¹.  The amount of memory may also be a
>>>>> function of the number of threads used (‘-j’).  So it could be that the
>>>>> build failed on a machine with less memory or more cores.
>>>>
>>>> The machine it failed on had 32 cores and 140GB of ram... but will
>>>> experiment with reducing parallelism on that machine and see if that
>>>> helps.
>>>
>>> I just realized that the Debian guix packages are built with parallelism
>>> disabled for reproducible builds, so that seems unlikely to be the
>>> issue... it might just be an issue with guile-2.2 on Debian...
>>
>> D’oh.  Could you try reducing the number of libgc marker thread, in case
>> that is what’s causing troubles?  You can do that by setting the
>> GC_MARKERS environment variables, as in GC_MARKERS=2.
>
> Is this issue still actual?
>
> If so, could you try what Ludovic suggested?  Otherwise, let's close it.

The Debian packages have since switched to use guile 3.0... I'll close
it for now.

Can always reopen if it starts happening again.

live well,
  vagrant