* bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
@ 2021-05-01 0:01 Vagrant Cascadian
2021-05-02 2:17 ` Vagrant Cascadian
0 siblings, 1 reply; 8+ messages in thread
From: Vagrant Cascadian @ 2021-05-01 0:01 UTC (permalink / raw)
To: 48131
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
I've been unable to build version 1.3.0rc1 for i386 on Debian:
[ 70%] GUILEC gnu/packages/direct-connect.go
[ 70%] GUILEC gnu/packages/disk.go
GC Warning: Failed to expand heap by 8388608 bytes
GC Warning: Failed to expand heap by 8388608 bytes
...
GC Warning: Failed to expand heap by 8388608 bytes
GC Warning: Failed to expand heap by 8388608 bytes
Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
make[3]: *** [Makefile:6871: make-go] Aborted
Debian is still using guile-2.2, so I'm guessing this is not a
particularly well tested codepath anymore...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
2021-05-01 0:01 bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2 Vagrant Cascadian
@ 2021-05-02 2:17 ` Vagrant Cascadian
2021-05-02 21:59 ` Ludovic Courtès
0 siblings, 1 reply; 8+ messages in thread
From: Vagrant Cascadian @ 2021-05-02 2:17 UTC (permalink / raw)
To: 48131
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On 2021-04-30, Vagrant Cascadian wrote:
> I've been unable to build version 1.3.0rc1 for i386 on Debian:
>
> [ 70%] GUILEC gnu/packages/direct-connect.go
> [ 70%] GUILEC gnu/packages/disk.go
> GC Warning: Failed to expand heap by 8388608 bytes
> GC Warning: Failed to expand heap by 8388608 bytes
> ...
> GC Warning: Failed to expand heap by 8388608 bytes
> GC Warning: Failed to expand heap by 8388608 bytes
> Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
> make[3]: *** [Makefile:6871: make-go] Aborted
>
>
> Debian is still using guile-2.2, so I'm guessing this is not a
> particularly well tested codepath anymore...
But strangely enough, it built fine on debian's build machines on all
supported architectures:
https://buildd.debian.org/status/package.php?p=guix&suite=experimental
*shrug*
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
2021-05-02 2:17 ` Vagrant Cascadian
@ 2021-05-02 21:59 ` Ludovic Courtès
2021-05-02 22:17 ` Vagrant Cascadian
0 siblings, 1 reply; 8+ messages in thread
From: Ludovic Courtès @ 2021-05-02 21:59 UTC (permalink / raw)
To: Vagrant Cascadian; +Cc: 48131
Hi!
Vagrant Cascadian <vagrant@debian.org> skribis:
> On 2021-04-30, Vagrant Cascadian wrote:
>> I've been unable to build version 1.3.0rc1 for i386 on Debian:
>>
>> [ 70%] GUILEC gnu/packages/direct-connect.go
>> [ 70%] GUILEC gnu/packages/disk.go
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> ...
>> GC Warning: Failed to expand heap by 8388608 bytes
>> GC Warning: Failed to expand heap by 8388608 bytes
>> Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
>> make[3]: *** [Makefile:6871: make-go] Aborted
>>
>>
>> Debian is still using guile-2.2, so I'm guessing this is not a
>> particularly well tested codepath anymore...
>
> But strangely enough, it built fine on debian's build machines on all
> supported architectures:
>
> https://buildd.debian.org/status/package.php?p=guix&suite=experimental
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.
Ludo’.
¹ https://wingolog.org/archives/2020/06/03/a-baseline-compiler-for-guile
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
2021-05-02 21:59 ` Ludovic Courtès
@ 2021-05-02 22:17 ` Vagrant Cascadian
2021-05-02 22:50 ` Vagrant Cascadian
0 siblings, 1 reply; 8+ messages in thread
From: Vagrant Cascadian @ 2021-05-02 22:17 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 48131
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
On 2021-05-02, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@debian.org> skribis:
>
>> On 2021-04-30, Vagrant Cascadian wrote:
>>> I've been unable to build version 1.3.0rc1 for i386 on Debian:
>>>
>>> [ 70%] GUILEC gnu/packages/direct-connect.go
>>> [ 70%] GUILEC gnu/packages/disk.go
>>> GC Warning: Failed to expand heap by 8388608 bytes
>>> GC Warning: Failed to expand heap by 8388608 bytes
>>> ...
>>> GC Warning: Failed to expand heap by 8388608 bytes
>>> GC Warning: Failed to expand heap by 8388608 bytes
>>> Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
>>> make[3]: *** [Makefile:6871: make-go] Aborted
>>>
>>>
>>> Debian is still using guile-2.2, so I'm guessing this is not a
>>> particularly well tested codepath anymore...
>>
>> But strangely enough, it built fine on debian's build machines on all
>> supported architectures:
>>
>> https://buildd.debian.org/status/package.php?p=guix&suite=experimental
>
> 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.
The buildd.debian.org machine used only four cores, not sure how much
ram it had.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
2021-05-02 22:17 ` Vagrant Cascadian
@ 2021-05-02 22:50 ` Vagrant Cascadian
2021-05-03 19:54 ` Ludovic Courtès
0 siblings, 1 reply; 8+ messages in thread
From: Vagrant Cascadian @ 2021-05-02 22:50 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 48131
[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]
On 2021-05-02, Vagrant Cascadian wrote:
> On 2021-05-02, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant@debian.org> skribis:
>>> On 2021-04-30, Vagrant Cascadian wrote:
>>>> I've been unable to build version 1.3.0rc1 for i386 on Debian:
>>>>
>>>> [ 70%] GUILEC gnu/packages/direct-connect.go
>>>> [ 70%] GUILEC gnu/packages/disk.go
>>>> GC Warning: Failed to expand heap by 8388608 bytes
>>>> GC Warning: Failed to expand heap by 8388608 bytes
>>>> ...
>>>> GC Warning: Failed to expand heap by 8388608 bytes
>>>> GC Warning: Failed to expand heap by 8388608 bytes
>>>> Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
>>>> make[3]: *** [Makefile:6871: make-go] Aborted
>>>>
>>>>
>>>> Debian is still using guile-2.2, so I'm guessing this is not a
>>>> particularly well tested codepath anymore...
>>>
>>> But strangely enough, it built fine on debian's build machines on all
>>> supported architectures:
>>>
>>> https://buildd.debian.org/status/package.php?p=guix&suite=experimental
>>
>> 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...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
2021-05-02 22:50 ` Vagrant Cascadian
@ 2021-05-03 19:54 ` Ludovic Courtès
2022-03-18 2:31 ` Maxim Cournoyer
0 siblings, 1 reply; 8+ messages in thread
From: Ludovic Courtès @ 2021-05-03 19:54 UTC (permalink / raw)
To: Vagrant Cascadian; +Cc: 48131
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.
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
2021-05-03 19:54 ` Ludovic Courtès
@ 2022-03-18 2:31 ` Maxim Cournoyer
2022-03-18 6:09 ` Vagrant Cascadian
0 siblings, 1 reply; 8+ messages in thread
From: Maxim Cournoyer @ 2022-03-18 2:31 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: Vagrant Cascadian, 48131
Hi Vagrant,
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.
Thank you,
Maxim
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
2022-03-18 2:31 ` Maxim Cournoyer
@ 2022-03-18 6:09 ` Vagrant Cascadian
0 siblings, 0 replies; 8+ messages in thread
From: Vagrant Cascadian @ 2022-03-18 6:09 UTC (permalink / raw)
To: Maxim Cournoyer, Ludovic Courtès; +Cc: 48131-done
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2022-03-18 6:11 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-05-01 0:01 bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2 Vagrant Cascadian
2021-05-02 2:17 ` Vagrant Cascadian
2021-05-02 21:59 ` Ludovic Courtès
2021-05-02 22:17 ` Vagrant Cascadian
2021-05-02 22:50 ` Vagrant Cascadian
2021-05-03 19:54 ` Ludovic Courtès
2022-03-18 2:31 ` Maxim Cournoyer
2022-03-18 6:09 ` Vagrant Cascadian
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).