all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christina O'Donnell <cdo@mutix.org>
Cc: 40316@debbugs.gnu.org,  guix-devel@gnu.org,
	 zhengjunjie@iscas.ac.cn, steve@futurile.net
Subject: Re: bug#40316: nss not reproducible
Date: Mon, 06 May 2024 12:12:01 +0200	[thread overview]
Message-ID: <8734qvl05q.fsf@gnu.org> (raw)
In-Reply-To: <265e4d6b-c83d-e477-3025-9d4f7187f849@mutix.org> (Christina O'Donnell's message of "Thu, 2 May 2024 16:20:45 +0100")

Hi,

Christina O'Donnell <cdo@mutix.org> skribis:

> Tangentially, given how long nss takes to build, do you think that
> it'd be worth shaving it down to a single test pass? Currently it runs
> each test up to 3 times, which takes ~1h on my machine with no other
> build running. Running only the standard pass takes 2.5-3x less time,
> which is a huge quality of life improvement.

Currently we run ./nss/tests/all.sh, which I suppose is what upstream
recommends to run tests.

For sure I’d be happy if the test suite could run faster, but does
upstream offer such an option?  When you say “a single pass”, is that
something upstream supports?

Thanks,
Ludo’.


  reply	other threads:[~2024-05-06 10:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 11:16 bug#40316: core-updates nss not reproducible Danny Milosavljevic
2020-03-30  6:09 ` Gábor Boskovits
2020-03-30 11:55 ` Marius Bakke
2020-03-31  9:28   ` Björn Höfling
2021-05-18  1:04 ` Bone Baboon via Bug reports for GNU Guix
2024-03-07 22:16   ` Vagrant Cascadian
2024-04-23 12:42 ` bug#40316: Update needed of NSS Steve George
2024-04-26 21:33 ` [PATCH 0/6] WIP: nss: Update to 3.99 Christina O'Donnell
2024-04-26 21:33   ` bug#40316: [PATCH 1/6] gnu: nss: Fix cross-compilation Christina O'Donnell
2024-04-26 21:33   ` bug#40316: [PATCH 2/6] gnu: nspr: " Christina O'Donnell
2024-04-26 21:33   ` [PATCH 3/6] gnu: nss: Make reproducible Christina O'Donnell
2024-04-26 22:58     ` bug#40316: " Vagrant Cascadian
2024-05-02 12:51       ` Christina O'Donnell
2024-04-26 21:34   ` [PATCH 4/6] gnu: nss: Update to 3.99 Christina O'Donnell
2024-04-26 21:34   ` [PATCH 5/6] gnu: nss-certs: " Christina O'Donnell
2024-04-26 21:34   ` [PATCH 6/6] WIP: nss: Attempting to resolve FIPS regression Christina O'Donnell
2024-05-02  8:15   ` bug#40316: nss not reproducible Ludovic Courtès
2024-05-02 15:20     ` Christina O'Donnell
2024-05-06 10:12       ` Ludovic Courtès [this message]
2024-05-06 11:37         ` Christina O'Donnell
2024-05-14  9:15           ` Ludovic Courtès
2024-05-05  8:00     ` Tobias Alexandra Platen
2024-05-02 11:00 ` bug#40316: [PATCH v2 0/6] Attempt to make nss reproducible Christina O'Donnell
2024-05-02 11:00   ` bug#40316: [PATCH v2 1/6] gnu: nss: Fix cross-compilation Christina O'Donnell
2024-05-02 11:00     ` bug#40316: [PATCH v2 2/6] gnu: nspr: " Christina O'Donnell
2024-05-02 11:00     ` bug#40316: [PATCH v2 3/6] gnu: nss: Update to 3.99 Christina O'Donnell
2024-05-02 11:00     ` bug#40316: [PATCH v2 4/6] gnu: nss-certs: " Christina O'Donnell
2024-05-02 11:00     ` bug#40316: [PATCH v2 5/6] gnu: nss: Attempt to disable FIPS Christina O'Donnell
2024-05-02 11:00     ` bug#40316: [PATCH v2 6/6] gnu: nss: Disable FIPS in lowhashtest Christina O'Donnell
2024-05-02 12:42   ` bug#40316: [PATCH v2 0/6] Attempt to make nss reproducible Christina O'Donnell
2024-05-02 15:15 ` bug#40316: [PATCH v4 0/5] gnu: nss: Make reproducible Christina O'Donnell
2024-05-02 15:15   ` bug#40316: [PATCH v4 1/5] gnu: nss: Fix cross-compilation Christina O'Donnell
2024-05-02 15:15   ` bug#40316: [PATCH v4 2/5] gnu: nspr: " Christina O'Donnell
2024-05-02 15:15   ` bug#40316: [PATCH v4 3/5] gnu: nss: Update to 3.99 Christina O'Donnell
2024-05-02 15:15   ` bug#40316: [PATCH v4 4/5] gnu: nss-certs: " Christina O'Donnell
2024-05-02 15:15   ` bug#40316: [PATCH v4 5/5] gnu: nss: Make reproducible Christina O'Donnell

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=8734qvl05q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=40316@debbugs.gnu.org \
    --cc=cdo@mutix.org \
    --cc=guix-devel@gnu.org \
    --cc=steve@futurile.net \
    --cc=zhengjunjie@iscas.ac.cn \
    /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.