On Wed, Oct 4, 2023 at 11:44 AM Martin Stransky <stran...@redhat.com> wrote:

> Hello guys,
>
> Is there's a way how to set requested amount of ram for koji builders?
>
> I'd like to use it as Firefox builds fail recently due low memory, like
> https://bugzilla.redhat.com/show_bug.cgi?id=2241690


I looked at the first linked build log in the ticket and it looks like the
build failed in the debuginfo extraction step. In that log, find-debuginfo
is called with -j3, and it could be that it ran out of memory because it
was trying to do 3 debuginfo extractions in parallel. You could try to
stick something like this in the spec file to tune it down:

# Require 32 GB of RAM per CPU core for debuginfo processing
%global _find_debuginfo_opts %limit_build -m 32768

... and see if it helps. With this, it should pass -j1 to find-debuginfo
when the builder has 32 GB RAM, -j2 when it has 64 GB etc.

If that doesn't work, then there's also the option of using -g1 to reduce
the binary sizes so they take less memory to process (but that makes
backtraces much worse so I'd only leave it for emergencies if you can't get
an important build out otherwise).

Another option is that there's a heavybuilder channel in koji, which has
beefier machines, but it has some significant capacity issues (only 2
aarch64 builders, iirc) so it would be best to avoid it, if possible.
Chromium and webkitgtk are using it and sometimes builds have to wait a
long time after each other, especially when building something for all
Fedora branches.

Hope this helps,
Kalev
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to