From: "Kent Fredric" <kentnl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Archive-Zip/
Date: Fri, 21 Aug 2020 08:26:59 +0000 (UTC) [thread overview]
Message-ID: <1597998402.98ef7ebb399b2ee5ae2df0dc539ddb9b7da34b8d.kentnl@gentoo> (raw)
commit: 98ef7ebb399b2ee5ae2df0dc539ddb9b7da34b8d
Author: Kent Fredric <kentnl <AT> gentoo <DOT> org>
AuthorDate: Fri Aug 21 08:26:01 2020 +0000
Commit: Kent Fredric <kentnl <AT> gentoo <DOT> org>
CommitDate: Fri Aug 21 08:26:42 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=98ef7ebb
dev-perl/Archive-Zip: Disable parallel tests re bug #738308
Seems there are a lot of ways concurrency in these tests can collide,
they share some 'test directory' magic which seems hard to fix without
being invasive
Closes: https://bugs.gentoo.org/738308
Bug: https://github.com/redhotpenguin/perl-Archive-Zip/issues/82
Package-Manager: Portage-2.3.103, Repoman-2.3.22
Signed-off-by: Kent Fredric <kentnl <AT> gentoo.org>
dev-perl/Archive-Zip/Archive-Zip-1.680.0.ebuild | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/dev-perl/Archive-Zip/Archive-Zip-1.680.0.ebuild b/dev-perl/Archive-Zip/Archive-Zip-1.680.0.ebuild
index 38e3c364bb7..02d2d78708b 100644
--- a/dev-perl/Archive-Zip/Archive-Zip-1.680.0.ebuild
+++ b/dev-perl/Archive-Zip/Archive-Zip-1.680.0.ebuild
@@ -31,3 +31,8 @@ BDEPEND="${RDEPEND}
>=virtual/perl-Test-Simple-0.880.0
)
"
+# Parallel tests broken
+# See:
+# https://bugs.gentoo.org/738308
+# https://github.com/redhotpenguin/perl-Archive-Zip/issues/82
+DIST_TEST="do"
next reply other threads:[~2020-08-21 8:27 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 8:26 Kent Fredric [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-12 12:26 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Archive-Zip/ WANG Xuerui
2021-04-17 22:43 Andreas K. Hüttel
2020-11-28 19:18 Sam James
2020-11-28 18:11 Sam James
2020-08-21 15:30 Agostino Sarubbo
2020-08-21 10:08 Sam James
2020-08-20 16:40 Sam James
2020-04-28 17:23 Kent Fredric
2020-04-15 7:08 Agostino Sarubbo
2019-08-01 13:09 Aaron Bauman
2019-07-22 13:58 Mikle Kolyada
2018-12-02 2:12 Kent Fredric
2018-11-29 17:44 Tobias Klausmann
2018-11-25 9:43 Mikle Kolyada
2018-11-24 11:00 Sergei Trofimovich
2018-11-24 10:49 Sergei Trofimovich
2018-11-24 10:45 Sergei Trofimovich
2018-11-24 10:39 Sergei Trofimovich
2018-11-23 20:30 Thomas Deutschmann
2018-11-23 16:18 Sergei Trofimovich
2018-11-23 13:49 Agostino Sarubbo
2018-10-15 16:05 Fabian Groffen
2018-09-30 1:20 Kent Fredric
2018-09-07 10:42 Kent Fredric
2018-04-24 2:20 Kent Fredric
2018-04-15 17:04 Mikle Kolyada
2018-04-07 21:18 Sergei Trofimovich
2018-04-07 21:13 Matt Turner
2018-04-07 4:36 Matt Turner
2018-04-07 4:36 Matt Turner
2018-04-05 16:10 Tobias Klausmann
2018-04-04 22:26 Sergei Trofimovich
2018-04-04 14:25 Aaron Bauman
2017-12-30 20:44 David Seifert
2017-12-30 11:04 Mikle Kolyada
2017-12-04 20:36 Kent Fredric
2017-12-04 7:30 Sergei Trofimovich
2017-12-04 7:30 Sergei Trofimovich
2017-12-03 19:50 Sergei Trofimovich
2017-09-16 18:09 Patrick Lauer
2017-08-27 15:34 Michael Palimaka
2017-07-18 16:22 Kent Fredric
2017-06-06 16:04 Markus Meier
2017-05-22 13:25 Tobias Klausmann
2017-05-22 10:49 Michael Weber
2017-05-22 10:39 Michael Weber
2017-05-20 8:49 Agostino Sarubbo
2017-04-01 16:51 Kent Fredric
2017-03-15 18:54 Matt Turner
2017-01-28 18:17 Kent Fredric
2016-11-05 14:30 Michael Palimaka
2016-08-16 1:37 Kent Fredric
2016-05-25 23:33 Matt Turner
2016-05-06 22:30 Andreas Hüttel
2016-02-29 18:53 Fabian Groffen
2016-01-24 9:06 Jeroen Roovers
2015-12-26 22:35 Andreas Hüttel
2015-12-26 22:22 Mikle Kolyada
2015-12-26 21:52 Andreas Hüttel
2015-09-29 21:08 Andreas Hüttel
2015-09-06 21:09 Andreas Hüttel
2015-08-10 23:59 Mikle Kolyada
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=1597998402.98ef7ebb399b2ee5ae2df0dc539ddb9b7da34b8d.kentnl@gentoo \
--to=kentnl@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