public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/source-highlight/
Date: Sat, 13 Apr 2019 13:57:36 +0000 (UTC)	[thread overview]
Message-ID: <1555163840.364ab66d47a0098019eb131714254a8b38a3afc4.dev-zero@gentoo> (raw)

commit:     364ab66d47a0098019eb131714254a8b38a3afc4
Author:     Tiziano Müller <dev-zero <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 13 13:56:35 2019 +0000
Commit:     Tiziano Müller <dev-zero <AT> gentoo <DOT> org>
CommitDate: Sat Apr 13 13:57:20 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=364ab66d

dev-util/source-highlight: serialize tests

Upstream uses the same intermediate files in multiple tests, running
them in parallel by make will eventually break one or more tests.

Closes: https://bugs.gentoo.org/635100
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Tiziano Müller <dev-zero <AT> gentoo.org>

 dev-util/source-highlight/source-highlight-3.1.8.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/dev-util/source-highlight/source-highlight-3.1.8.ebuild b/dev-util/source-highlight/source-highlight-3.1.8.ebuild
index 4cc9a772630..4f6024727e8 100644
--- a/dev-util/source-highlight/source-highlight-3.1.8.ebuild
+++ b/dev-util/source-highlight/source-highlight-3.1.8.ebuild
@@ -44,5 +44,7 @@ src_install () {
 
 src_test() {
 	export LD_LIBRARY_PATH="${S}/lib/srchilite/.libs/"
-	default
+	# upstream uses the same temporary filenames in numerous places
+	# see https://bugs.gentoo.org/635100
+	emake -j1 check
 }


             reply	other threads:[~2019-04-13 13:57 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13 13:57 Tiziano Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-12 19:05 [gentoo-commits] repo/gentoo:master commit in: dev-util/source-highlight/ Arthur Zamarin
2024-02-03  6:56 Sam James
2024-02-02 17:51 Arthur Zamarin
2024-02-02 14:46 Arthur Zamarin
2024-02-02  4:51 Sam James
2024-02-02  4:51 Sam James
2024-02-02  4:44 Sam James
2024-02-02  4:44 Sam James
2024-02-02  4:44 Sam James
2024-02-02  4:44 Sam James
2023-12-28  2:19 Sam James
2023-12-28  2:19 Sam James
2023-12-28  2:19 Sam James
2023-12-28  2:19 Sam James
2023-12-28  2:19 Sam James
2022-05-10  0:44 WANG Xuerui
2021-07-19 23:14 Marek Szuba
2021-01-06 22:55 Fabian Groffen
2020-07-25  9:18 Sergei Trofimovich
2020-07-18 18:09 Sam James
2020-06-28 20:44 Agostino Sarubbo
2020-06-28 20:37 Agostino Sarubbo
2020-06-28 20:33 Agostino Sarubbo
2020-06-28 20:30 Agostino Sarubbo
2020-06-25  7:00 Agostino Sarubbo
2020-06-24 17:22 Sergei Trofimovich
2020-06-22 18:23 Sergei Trofimovich
2020-03-23 23:58 Sergei Trofimovich
2019-11-29 23:12 Sergei Trofimovich
2019-11-29 23:03 Sergei Trofimovich
2019-11-29 20:50 Sergei Trofimovich
2019-11-29 20:37 Sergei Trofimovich
2019-11-18  2:18 Aaron Bauman
2019-04-17 20:01 Sergei Trofimovich
2019-04-09  9:48 Fabian Groffen
2018-05-13 10:44 Mart Raudsepp
2017-11-25 19:03 Sergei Trofimovich
2017-10-25 23:53 Manuel Rüger
2017-10-23 21:00 Sergei Trofimovich
2017-10-22 20:33 Thomas Deutschmann
2017-10-19  5:00 Markus Meier
2017-10-15 21:42 Sergei Trofimovich
2017-10-14 14:10 Sergei Trofimovich
2016-10-08 18:44 David Seifert

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=1555163840.364ab66d47a0098019eb131714254a8b38a3afc4.dev-zero@gentoo \
    --to=dev-zero@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