From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/uutils-coreutils/
Date: Tue, 28 Jan 2025 12:21:31 +0000 (UTC) [thread overview]
Message-ID: <1738066735.0966fc6cbc9c730c8a45dcd5ff299d5d9c091be7.sam@gentoo> (raw)
commit: 0966fc6cbc9c730c8a45dcd5ff299d5d9c091be7
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 28 12:18:55 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jan 28 12:18:55 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0966fc6c
sys-apps/uutils-coreutils: set NEXTEST_TEST_THREADS
Otherwise, test execution jobs use all available cores.
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-apps/uutils-coreutils/uutils-coreutils-0.0.29.ebuild | 3 ++-
sys-apps/uutils-coreutils/uutils-coreutils-9999.ebuild | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/sys-apps/uutils-coreutils/uutils-coreutils-0.0.29.ebuild b/sys-apps/uutils-coreutils/uutils-coreutils-0.0.29.ebuild
index e62645b6edfa..89cac79fa4c6 100644
--- a/sys-apps/uutils-coreutils/uutils-coreutils-0.0.29.ebuild
+++ b/sys-apps/uutils-coreutils/uutils-coreutils-0.0.29.ebuild
@@ -312,7 +312,7 @@ CRATES="
zopfli@0.8.1
"
-inherit cargo flag-o-matic
+inherit cargo flag-o-matic multiprocessing
DESCRIPTION="GNU coreutils rewritten in Rust"
HOMEPAGE="https://uutils.github.io/coreutils/ https://github.com/uutils/coreutils"
@@ -400,6 +400,7 @@ src_compile() {
src_test() {
local -x RUST_BACKTRACE=full
+ local -x NEXTEST_TEST_THREADS="$(makeopts_jobs)"
# Nicer output for nextest vs test
emake "${makeargs[@]}" \
diff --git a/sys-apps/uutils-coreutils/uutils-coreutils-9999.ebuild b/sys-apps/uutils-coreutils/uutils-coreutils-9999.ebuild
index e62645b6edfa..89cac79fa4c6 100644
--- a/sys-apps/uutils-coreutils/uutils-coreutils-9999.ebuild
+++ b/sys-apps/uutils-coreutils/uutils-coreutils-9999.ebuild
@@ -312,7 +312,7 @@ CRATES="
zopfli@0.8.1
"
-inherit cargo flag-o-matic
+inherit cargo flag-o-matic multiprocessing
DESCRIPTION="GNU coreutils rewritten in Rust"
HOMEPAGE="https://uutils.github.io/coreutils/ https://github.com/uutils/coreutils"
@@ -400,6 +400,7 @@ src_compile() {
src_test() {
local -x RUST_BACKTRACE=full
+ local -x NEXTEST_TEST_THREADS="$(makeopts_jobs)"
# Nicer output for nextest vs test
emake "${makeargs[@]}" \
next reply other threads:[~2025-01-28 12:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 12:21 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-25 20:18 [gentoo-commits] repo/gentoo:master commit in: sys-apps/uutils-coreutils/ Luca Barbato
2025-04-10 0:12 Sam James
2025-03-14 5:26 Sam James
2025-01-19 0:17 Sam James
2024-03-05 4:48 Sam James
2024-03-05 4:48 Sam James
2024-03-02 5:05 Sam James
2024-02-02 1:18 Sam James
2023-12-28 3:43 Sam James
2023-11-25 4:49 Sam James
2023-11-25 4:49 Sam James
2023-10-16 4:06 Sam James
2023-10-16 4:06 Sam James
2023-10-06 18:17 Sam James
2023-10-06 18:08 Sam James
2023-09-04 13:20 Sam James
2023-09-04 13:20 Sam James
2023-07-15 15:55 Sam James
2023-06-24 12:35 Arthur Zamarin
2023-06-05 3:50 Sam James
2023-06-03 5:42 Sam James
2023-04-02 20:44 Sam James
2023-02-22 17:51 Sam James
2023-02-22 17:51 Sam James
2023-02-22 9:10 Sam James
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=1738066735.0966fc6cbc9c730c8a45dcd5ff299d5d9c091be7.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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