public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/netcdf/
Date: Sat, 15 Jul 2017 10:25:14 +0000 (UTC)	[thread overview]
Message-ID: <1500114310.c2f1593960a02f1e374e0751457be58cf66f8700.slyfox@gentoo> (raw)

commit:     c2f1593960a02f1e374e0751457be58cf66f8700
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 15 10:24:59 2017 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Jul 15 10:25:10 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2f15939

sci-libs/netcdf: make tests sequential, bug #621486

Parallel tests fail consistently on 4-core and 8-core systems.
I suspect same temporary file reuse.

Bug: https://bugs.gentoo.org/621486
Package-Manager: Portage-2.3.6, Repoman-2.3.2

 sci-libs/netcdf/netcdf-4.4.1.1.ebuild | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/sci-libs/netcdf/netcdf-4.4.1.1.ebuild b/sci-libs/netcdf/netcdf-4.4.1.1.ebuild
index 703031c4062..b295062f6d9 100644
--- a/sci-libs/netcdf/netcdf-4.4.1.1.ebuild
+++ b/sci-libs/netcdf/netcdf-4.4.1.1.ebuild
@@ -43,6 +43,11 @@ src_configure() {
 		$(use_enable tools utilities)
 }
 
+src_test() {
+	# fails parallel tests: bug #621486
+	emake check -j1
+}
+
 src_install() {
 	default
 	use examples && dodoc -r examples


             reply	other threads:[~2017-07-15 10:25 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15 10:25 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-18 22:21 [gentoo-commits] repo/gentoo:master commit in: sci-libs/netcdf/ Jakov Smolić
2024-10-19 17:33 Michał Górny
2024-07-27  7:07 Arthur Zamarin
2024-05-30  4:36 Ionen Wolkens
2024-05-29 23:46 Sam James
2024-04-02 11:29 Sam James
2023-03-31 11:42 Arthur Zamarin
2023-03-31 11:42 Arthur Zamarin
2023-03-16 17:41 Arthur Zamarin
2023-03-15 10:50 Sam James
2023-03-15  5:53 Sam James
2023-03-15  5:45 Sam James
2023-03-05  4:13 Sam James
2022-06-13  7:12 Agostino Sarubbo
2022-06-13  7:07 Agostino Sarubbo
2022-06-11  5:02 Sam James
2022-06-08  5:25 Sam James
2022-05-11  8:02 Agostino Sarubbo
2022-05-10 13:47 Agostino Sarubbo
2022-01-11 21:37 Jakov Smolić
2022-01-11 21:37 Jakov Smolić
2021-12-28 22:00 Sam James
2021-12-28 22:00 Sam James
2021-08-14 23:15 Marek Szuba
2021-02-25 19:07 Sam James
2021-02-25  8:56 Sam James
2021-02-25  8:56 Sam James
2021-02-25  8:50 Sam James
2021-02-22 18:57 Sam James
2021-02-19 20:12 Thomas Deutschmann
2021-01-17 13:37 Pacho Ramos
2021-01-17 13:37 Pacho Ramos
2020-12-28 16:11 David Seifert
2019-09-14  6:52 Matt Turner
2018-10-13 15:49 Sergei Trofimovich
2018-10-05 17:11 Mikle Kolyada
2018-10-05 12:25 Thomas Deutschmann
2018-09-30 10:10 Pacho Ramos
2018-05-16 22:57 Aaron Bauman
2018-04-24 16:19 Matthias Maier
2018-04-24 15:58 Matthias Maier
2017-08-27 14:03 Sergei Trofimovich
2017-07-15 10:10 Sergei Trofimovich
2016-12-28 11:25 Pacho Ramos
2016-12-28 11:25 Pacho Ramos
2016-12-28 11:25 Pacho Ramos
2016-01-25  9:52 David Seifert
2016-01-23 20:05 David Seifert
2016-01-20  8:20 Justin Lecher

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=1500114310.c2f1593960a02f1e374e0751457be58cf66f8700.slyfox@gentoo \
    --to=slyfox@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