From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/cpio/
Date: Thu, 18 Jan 2024 03:22:25 +0000 (UTC) [thread overview]
Message-ID: <1705547959.226fcb9d41b4be413a80adac41ddcf090f260bae.sam@gentoo> (raw)
commit: 226fcb9d41b4be413a80adac41ddcf090f260bae
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 18 02:57:48 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jan 18 03:19:19 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=226fcb9d
app-arch/cpio: run tests in parallel
Inspired by vapier's cd7f047fe43fb631c4ca6979c6efb5038c616f41. `RUNTESTFLAGS`
has been in the back of my head for a while now as I've been meaning to figure out
the interaction between it and parallel make and which packages actually need it.
This only shaves off about ~10s or so consistently for me for cpio though, as
its test suite is smaller, but maybe it'll do better on slower machines.
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-arch/cpio/cpio-2.15.ebuild | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/app-arch/cpio/cpio-2.15.ebuild b/app-arch/cpio/cpio-2.15.ebuild
index e9733b098ca1..6f98be317e83 100644
--- a/app-arch/cpio/cpio-2.15.ebuild
+++ b/app-arch/cpio/cpio-2.15.ebuild
@@ -3,6 +3,8 @@
EAPI=8
+inherit multiprocessing
+
DESCRIPTION="File archival tool which can also read and write tar files"
HOMEPAGE="https://www.gnu.org/software/cpio/cpio.html"
SRC_URI="mirror://gnu/cpio/${P}.tar.bz2"
@@ -39,6 +41,10 @@ src_configure() {
econf "${myeconfargs[@]}"
}
+src_test() {
+ emake check TESTSUITEFLAGS="--jobs=$(get_makeopts_jobs)"
+}
+
pkg_postinst() {
# Ensure to preserve the symlink before app-alternatives/cpio
# is installed
next reply other threads:[~2024-01-18 3:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 3:22 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-17 5:47 [gentoo-commits] repo/gentoo:master commit in: app-arch/cpio/ Sam James
2024-03-02 17:08 Arthur Zamarin
2024-02-18 13:31 Sam James
2024-01-14 18:29 Sam James
2023-06-17 19:44 Arthur Zamarin
2023-06-17 15:13 Sam James
2023-06-17 11:43 Arthur Zamarin
2023-06-17 8:29 Arthur Zamarin
2023-06-17 7:43 Arthur Zamarin
2023-06-17 6:12 Sam James
2023-06-17 5:57 Sam James
2023-06-17 5:57 Sam James
2022-12-27 19:53 Sam James
2022-12-27 19:45 Sam James
2022-12-27 13:40 Sam James
2022-12-27 11:31 Sam James
2022-11-28 14:31 Michał Górny
2022-10-30 16:31 Sam James
2022-10-30 16:31 Sam James
2022-10-30 15:51 Sam James
2022-10-30 9:55 Sam James
2022-09-21 4:21 Sam James
2022-05-07 11:14 WANG Xuerui
2022-05-05 10:17 WANG Xuerui
2021-09-23 22:47 Marek Szuba
2021-03-23 13:20 Lars Wendler
2021-01-06 12:52 Fabian Groffen
2020-12-27 13:34 Fabian Groffen
2019-11-14 22:39 Sergei Trofimovich
2019-11-14 16:16 Lars Wendler
2019-11-14 16:16 Lars Wendler
2019-11-14 15:41 Agostino Sarubbo
2019-11-14 15:17 Aaron Bauman
2019-11-06 15:51 Lars Wendler
2016-11-16 3:59 Mike Frysinger
2016-03-14 20:00 Tobias Klausmann
2016-02-20 14:26 Markus Meier
2016-02-20 12:13 Richard Freeman
2016-02-17 16:47 Jeroen Roovers
2016-02-14 19:48 Mike Frysinger
2015-09-11 5:33 Mike Frysinger
2015-09-11 5:33 Mike Frysinger
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=1705547959.226fcb9d41b4be413a80adac41ddcf090f260bae.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