From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/autoconf-dickey/
Date: Fri, 9 Sep 2022 14:43:29 +0000 (UTC) [thread overview]
Message-ID: <1662734587.881a6712cd47c459923415c8c86e3bd3d8aa0d3b.sam@gentoo> (raw)
commit: 881a6712cd47c459923415c8c86e3bd3d8aa0d3b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Sep 9 14:43:07 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Sep 9 14:43:07 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=881a6712
sys-devel/autoconf-dickey: force -j1 for tests
They still fail, but very differently. May just be because
of grep 3.8.
Closes: https://bugs.gentoo.org/869278
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-devel/autoconf-dickey/autoconf-dickey-2.52_p20210509.ebuild | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/sys-devel/autoconf-dickey/autoconf-dickey-2.52_p20210509.ebuild b/sys-devel/autoconf-dickey/autoconf-dickey-2.52_p20210509.ebuild
index c02432050d58..f3ca0509bac2 100644
--- a/sys-devel/autoconf-dickey/autoconf-dickey-2.52_p20210509.ebuild
+++ b/sys-devel/autoconf-dickey/autoconf-dickey-2.52_p20210509.ebuild
@@ -39,3 +39,8 @@ src_configure() {
econf "${myeconfargs[@]}"
}
+
+src_test() {
+ # -j1 for bug #869278
+ emake -j1 check
+}
next reply other threads:[~2022-09-09 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 14:43 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-16 3:30 [gentoo-commits] repo/gentoo:master commit in: sys-devel/autoconf-dickey/ Sam James
2022-12-06 20:32 Sam James
2022-12-06 16:55 Sam James
2022-12-06 16:55 Sam James
2022-11-18 3:37 Sam James
2022-09-09 6:14 Fabian Groffen
2022-09-09 5:52 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=1662734587.881a6712cd47c459923415c8c86e3bd3d8aa0d3b.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