build failure: 1.3.0rc1 on Debian i386 with guile-2.2

  • Done
  • quality assurance status badge
Details
3 participants
  • Ludovic Courtès
  • Maxim Cournoyer
  • Vagrant Cascadian
Owner
unassigned
Submitted by
Vagrant Cascadian
Severity
normal
V
V
Vagrant Cascadian wrote on 1 May 2021 02:01
(address . bug-guix@gnu.org)
875z03wcco.fsf@yucca
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
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYIyaeAAKCRDcUY/If5cW
qiuDAQCT8xVadU6wb/vb1kUZVQPSxYUxdUYvKYjCwdnUrVtLOgEApvbWUBar2/4S
f6O8DanAg7Apt9PXTRvjdKjzmVDcqAE=
=l9+r
-----END PGP SIGNATURE-----

V
V
Vagrant Cascadian wrote on 2 May 2021 04:17
(address . 48131@debbugs.gnu.org)
87h7jlvpzr.fsf@yucca
On 2021-04-30, Vagrant Cascadian wrote:
Toggle quote (16 lines)
> 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:


*shrug*


live well,
vagrant
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYI4LqQAKCRDcUY/If5cW
qsIxAP48QhZ0pb+lmO1NzkUNODNRKv2SlbZrjgoQtcITbB+eAQD6A4+VcGCo2bI8
0IIv+uLNUyvb/yQc2LHWZoUOpuBTsAk=
=TJOJ
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 2 May 2021 23:59
Re: bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
(name . Vagrant Cascadian)(address . vagrant@debian.org)(address . 48131@debbugs.gnu.org)
8735v423vw.fsf@gnu.org
Hi!

Vagrant Cascadian <vagrant@debian.org> skribis:

Toggle quote (22 lines)
> 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’.

V
V
Vagrant Cascadian wrote on 3 May 2021 00:17
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 48131@debbugs.gnu.org)
87mttcu6es.fsf@yucca
On 2021-05-02, Ludovic Courtès wrote:
Toggle quote (29 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYI8lCwAKCRDcUY/If5cW
qgosAP0eEWR9dmBP4uwjKFYohe34yICJfuTqTfkbVc2tJZrLeQD6A3TDy2NlHK+l
XmaHB4GjK3+s6JpH/KBRSyQwRbb2Xwg=
=iDG0
-----END PGP SIGNATURE-----

V
V
Vagrant Cascadian wrote on 3 May 2021 00:50
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 48131@debbugs.gnu.org)
87k0ogu4wa.fsf@yucca
On 2021-05-02, Vagrant Cascadian wrote:
Toggle quote (33 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYI8stQAKCRDcUY/If5cW
qm4wAQC2O20sPWjLYw3OV+t6U+7ijbwFXwhZl20Aqi9lMFhSlwEAqjNFKOYxWONZ
UCknzRy9xf7Z4w2wRpgFN36xaZkFvQY=
=qxQf
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 3 May 2021 21:54
(name . Vagrant Cascadian)(address . vagrant@debian.org)(address . 48131@debbugs.gnu.org)
87fsz3wq2m.fsf@gnu.org
Vagrant Cascadian <vagrant@debian.org> skribis:

Toggle quote (3 lines)
> On 2021-05-02, Vagrant Cascadian wrote:
>> On 2021-05-02, Ludovic Courtès wrote:

[...]

Toggle quote (13 lines)
>>> 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’.
M
M
Maxim Cournoyer wrote on 18 Mar 2022 03:31
(name . Ludovic Courtès)(address . ludo@gnu.org)
87lex86lfg.fsf@gmail.com
Hi Vagrant,

Ludovic Courtès <ludo@gnu.org> writes:

Toggle quote (24 lines)
> 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
V
V
Vagrant Cascadian wrote on 18 Mar 2022 07:09
(address . 48131-done@debbugs.gnu.org)
87czijyeor.fsf@contorta
On 2022-03-17, Maxim Cournoyer wrote:
Toggle quote (25 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYjQiJQAKCRDcUY/If5cW
qr54APoDbRSUO0HpebOzU8XBL70N4M6hGOpQw0aAzdbpplTTJQEAmMHh73P39pmS
5bih96pz63oKkQXVcaAFt4tJ5GGrEAc=
=dy7f
-----END PGP SIGNATURE-----

Closed
?