all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ryan Sundberg via Guix-patches via <guix-patches@gnu.org>
To: 74618@debbugs.gnu.org
Cc: Ryan Sundberg <ryan@arctype.co>
Subject: [bug#74618] [PATCH] gnu: lcov: disable parallel tests
Date: Sun,  1 Dec 2024 21:29:39 -0800	[thread overview]
Message-ID: <20abb9b1d79ab562fba8e6282d33de853cd78f05.1733117293.git.ryan@arctype.co> (raw)
In-Reply-To: <8afcc0bf2961c2b93a41289a8cec7e5a28957b70.1732951981.git.ryan@arctype.co>

`make check` is not reliable for lcov when run in parallel
(e.g. `make -j 24 check`). Disable parallelism for the test suite.

* gnu/packages/code (lcov): Set #:parallel-tests? #f

Signed-off-by: Ryan Sundberg <ryan@arctype.co>
Change-Id: Ibb3618c4786dfbb50b90e725297947458115347c
---
 gnu/packages/code.scm | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gnu/packages/code.scm b/gnu/packages/code.scm
index 04ca4dfd6b..2ad1d8616a 100644
--- a/gnu/packages/code.scm
+++ b/gnu/packages/code.scm
@@ -556,6 +556,9 @@ (define-public lcov
      '(#:test-target "test"
        #:make-flags (list (string-append "PREFIX="
                                          (assoc-ref %outputs "out")))
+       ;; This test suite has race conditions in its scripts which make it
+       ;; unreliable when run in parallel.
+       #:parallel-tests? #f
        #:phases
        (modify-phases %standard-phases
          (add-after 'unpack 'patch-references-to-commands

base-commit: ce877a777e6ec089dc347e9883387d3080b471cf
-- 
2.41.0





  parent reply	other threads:[~2024-12-02  5:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-30  7:33 [bug#74618] [PATCH] gnu: lcov: disable parallel tests Ryan Sundberg via Guix-patches via
2024-12-01 10:45 ` Zheng Junjie
2024-12-02  5:29 ` Ryan Sundberg via Guix-patches via [this message]
2024-12-07  1:41   ` Zheng Junjie

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=20abb9b1d79ab562fba8e6282d33de853cd78f05.1733117293.git.ryan@arctype.co \
    --to=guix-patches@gnu.org \
    --cc=74618@debbugs.gnu.org \
    --cc=ryan@arctype.co \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.