public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/rust-coreutils] epel10: Set a memory-per-process constraint to help low-memory builders
Date: Thu, 06 Aug 2026 14:27:05 GMT [thread overview]
Message-ID: <178602642588.1.13543940511926462037.rpms-rust-coreutils-028efa8e31f4@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/rust-coreutils
Branch : epel10
Commit : 028efa8e31f450d5301c169ea3b3b28abde940c9
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-05-11T10:10:11+01:00
Stats : +6/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/rust-coreutils/c/028efa8e31f450d5301c169ea3b3b28abde940c9?branch=epel10
Log:
Set a memory-per-process constraint to help low-memory builders
---
diff --git a/rust-coreutils.spec b/rust-coreutils.spec
index 0eb252c..19960b2 100644
--- a/rust-coreutils.spec
+++ b/rust-coreutils.spec
@@ -14,6 +14,12 @@
%global feature_flags feat_acl,feat_os_unix,feat_selinux,uudoc
%endif
+# Peak memory usage is (on x86_64) roughly 4–5 GB in two parallel rustc
+# processes, building the uudoc and coreutils crates. This is OK on the
+# primary-architecture koji builders, but on more severely memory-constrained
+# systems (like some in RISC-V koji) this may cause swapping or memory
+# exhaustion. Setting a conservative memory limit per process helps.
+%global _smp_tasksize_proc 8192
%ifarch s390x
# the default setting causes the build to get killed
%global rustflags_debuginfo 1
reply other threads:[~2026-08-06 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178602642588.1.13543940511926462037.rpms-rust-coreutils-028efa8e31f4@fedoraproject.org \
--to=code@musicinmybrain.net \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox