Unfortunately, building large projects that use Rust with full debuginfo
tends to push the memory limits of our builders. The peak memory usage
is usually at link time, so reducing the number of parallel jobs isn’t
helpful. For now, reducing the debuginfo level as suggested seems to be
the best way to kick the can down the road until (hopefully, someday)
builders can be allocated more memory.
The ppc64le architecture is often the first affected since its builders
tend to have a little less available memory, but high memory usage from
debugging symbols happens on all architectures. For uv, I have to set
rustflags_debuginfo to 1 across the board. Even that barely works on
some of the more memory-constrained builders. I spent some time looking
for clever ideas that could make time-memory tradeoffs and came up
empty-handed.
On 11/12/24 9:23 AM, Eike Rathke wrote:
Hi,
On Monday, 2024-11-11 21:58:25 +0100, Kalev Lember wrote:
On Mon, Nov 11, 2024 at 5:35 PM Dan Horák <dan@xxxxxxxx> wrote:
I suppose it's similar to the issues Firefox is having and that's OOM
during compiling the Rust code ...
It might be possible to work this around by sticking
%ifarch ppc64le
%global rustflags_debuginfo 1
%endif
at the top of the spec file. Can you try if it helps, Eike?
That worked at least in a scratch build for rawhide. I'll try that again
with the next update.
Thanks!
Eike
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
