Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #389965 > unrolled thread

Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101

Back to article view | Back to linux.debian.bugs.rc

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101 Mike Hommey <mh@glandium.org> - 2025-04-16 23:10 +0200
    Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101 Santiago Vila <sanvila@debian.org> - 2025-04-16 23:40 +0200
      Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101 Lucas Nussbaum <lucas@debian.org> - 2025-04-17 00:00 +0200

#389965 — Bug#1103360: firefox-esr: FTBFS in testing/arm64: make[6]: *** [/build/reproducible-path/firefox-esr-128.9.0esr/config/makefiles/rust.mk:500: force-cargo-library-build] Error 101

On Wed, Apr 16, 2025 at 08:40:14PM +0200, Lucas Nussbaum wrote:
> Source: firefox-esr
> Version: 128.9.0esr-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lucas@debian.org
> Usertags: ftbfs-20250416 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in testing (trixie), your package failed
> to build on arm64.

The most relevant part of the log says: (signal: 9, SIGKILL: kill)

This was OOM killed. IOW, not enough memory on the builder you used.

Is this something that runs on buildds or some other machines?

Mike

[toc] | [next] | [standalone]

#389966

El 16/4/25 a las 23:07, Mike Hommey escribió:
> The most relevant part of the log says: (signal: 9, SIGKILL: kill)
> 
> This was OOM killed. IOW, not enough memory on the builder you used.
> 
> Is this something that runs on buildds or some other machines?

Hi. This is an archive rebuild for QA purposes, not the build which
happens in the official buildds.

I see by looking at the build log that the machine has 16GB of RAM
and probably no swap. This is more or less the memory required to build
firefox-esr on a machine with 1 CPU, so I'm not surprised that the
build is killed because not having enough memory.

[ I know how much memory firefox-esr needs because I collect
memory usage statistics during my own archive rebuilds ]

More CPUs usually makes the memory consumption higher.

Does the machine really have 0 cores, as shown in the build log?

DC-System-Info: 0 cores (), 16007536 kB RAM

Can anybody see the parallelism being used in the build log?

Maybe this should not be RC, but in either case it might be worth
to be investigated more.

Thanks.

[toc] | [prev] | [next] | [standalone]

#389969

On 16/04/25 at 23:30 +0200, Santiago Vila wrote:
> El 16/4/25 a las 23:07, Mike Hommey escribió:
> > The most relevant part of the log says: (signal: 9, SIGKILL: kill)
> > 
> > This was OOM killed. IOW, not enough memory on the builder you used.
> > 
> > Is this something that runs on buildds or some other machines?
> 
> Hi. This is an archive rebuild for QA purposes, not the build which
> happens in the official buildds.
> 
> I see by looking at the build log that the machine has 16GB of RAM
> and probably no swap. This is more or less the memory required to build
> firefox-esr on a machine with 1 CPU, so I'm not surprised that the
> build is killed because not having enough memory.
> 
> [ I know how much memory firefox-esr needs because I collect
> memory usage statistics during my own archive rebuilds ]
> 
> More CPUs usually makes the memory consumption higher.
> 
> Does the machine really have 0 cores, as shown in the build log?

No it has four cores. It's a bug in the script that generates the
header.

> DC-System-Info: 0 cores (), 16007536 kB RAM
> 
> Can anybody see the parallelism being used in the build log?
> 
> Maybe this should not be RC,

Yes

> but in either case it might be worth
> to be investigated more.

I'll do my next ARM rebuild with more RAM.

Lucas

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web