public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_test/
Date: Thu, 24 Aug 2017 19:02:04 +0000 (UTC)	[thread overview]
Message-ID: <1503601035.53b55350b50b480aae6f4e2ae9c93b023d8b02c1.gokturk@gentoo> (raw)

commit:     53b55350b50b480aae6f4e2ae9c93b023d8b02c1
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun May  7 18:51:48 2017 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Thu Aug 24 18:57:15 2017 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=53b55350

ebuild-writing/.../src_test: Do not encourage make, use 'emake -j1' instead

Replace the call to 'make' with 'emake -j1'. This was an old, bad
recommendation. Furthermore, remove the whole paragraph suggesting
not to use emake -- nowadays, most of the test suites work fine
in parallel.

 ebuild-writing/functions/src_test/text.xml | 10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/ebuild-writing/functions/src_test/text.xml b/ebuild-writing/functions/src_test/text.xml
index 70b6212..ca13a07 100644
--- a/ebuild-writing/functions/src_test/text.xml
+++ b/ebuild-writing/functions/src_test/text.xml
@@ -65,8 +65,8 @@ src_test() {
     sed -i -e 's~test49.out~~g' Makefile || die
 
     # Try to run the non-gui tests only
-    make test-nongui \
-            || die "At least one test failed"
+    # pass -j1 if tests do not support being run in parallel
+    emake -j1 test-nongui
 }
 </codesample>
 </body>
@@ -96,12 +96,6 @@ using <c>sed</c> or skipping a particular <c>make</c> target is
 sufficient.
 </p>
 
-<note>
-<c>emake</c> should not be used for <c>src_test</c> <d/> trying to
-parallelise tests unless the <c>Makefile</c> was specifically designed
-for this can cause all sorts of strange problems.
-</note>
-
 <p>
 Try to ensure that tests work properly for your ebuild. A good test
 suite is extremely helpful for arch maintainers.


             reply	other threads:[~2017-08-24 19:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 19:02 Göktürk Yüksek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-01  9:55 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_test/ Ulrich Müller
2021-08-01  9:51 Ulrich Müller
2021-07-06  8:03 Ulrich Müller
2021-01-03 13:57 Ulrich Müller
2020-08-28 19:02 Ulrich Müller
2020-08-19 17:32 Ulrich Müller
2017-08-24 19:08 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek

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=1503601035.53b55350b50b480aae6f4e2ae9c93b023d8b02c1.gokturk@gentoo \
    --to=gokturk@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