all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christina O'Donnell <cdo@mutix.org>
To: Christopher Baines <mail@cbaines.net>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 70663@debbugs.gnu.org
Subject: bug#70663: nss@3.99 is really hard to build
Date: Thu, 2 May 2024 21:38:45 +0100	[thread overview]
Message-ID: <cf5c17ef-964d-6957-9c40-4a50ef1ed019@mutix.org> (raw)
In-Reply-To: <87edalv4hj.fsf@cbaines.net>

Hi,

On 01/05/2024 18:14, Christopher Baines wrote:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi Chris,
>>
>> Christopher Baines <mail@cbaines.net> writes:
>>
>>> nss@3.99 is really hard to build, it's so hard and so important that
>>> data.guix.gnu.org is still after two days trying to process [1]. I say
>>> so important because you have to build nss@3.99 to compute the channel
>>> instance derivations for Guix.
>> I agree that the nss test suite takes a ridiculous amount of time to run
>> (multiple hours on a fast machine IIRC).  Are we missing a '--fast' test
>> flag or something to make it run in a more reasonable amount of time?
> I did read some of the all.sh script used for the tests and there is
> some environment variables you can set here:
>
>    https://github.com/nss-dev/nss/blob/master/tests/all.sh#L70-L82
>
> It seems like there are 4 "cycles", maybe we could just run the standard
> cycle or at least check how long they each take.

On my machine building natively on x86_64 I was getting approximately 63 
mins for a full test and 20 mins for just the 'standard' 'cycle'. My 
vote would be to just run 'standard' since that runs all of the tests once.

I can profile individual tests if needed to see if there's any that are 
particularly worth culling, but just the above change is an easy win 
without sacrificing too much test coverage.

Kind regards,

Christina





  reply	other threads:[~2024-05-02 20:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  9:16 bug#70663: nss@3.99 is really hard to build Christopher Baines
2024-05-01 10:11 ` Christopher Baines
2024-05-01 16:54 ` Maxim Cournoyer
2024-05-01 17:14   ` Christopher Baines
2024-05-02 20:38     ` Christina O'Donnell [this message]
2024-05-09 17:01       ` Joshua Branson via Bug reports for GNU Guix
2024-05-14  9:05 ` Christopher Baines
2024-05-14 10:36   ` pelzflorian (Florian Pelz)
2024-05-14 13:37     ` Christopher Baines
2024-05-14 12:58   ` Maxim Cournoyer
2024-05-14 13:33     ` Christopher Baines
2024-05-14 15:03     ` Mark H Weaver
2024-05-16  2:44       ` Maxim Cournoyer
2024-05-16  4:02         ` Ian Eure

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=cf5c17ef-964d-6957-9c40-4a50ef1ed019@mutix.org \
    --to=cdo@mutix.org \
    --cc=70663@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    --cc=maxim.cournoyer@gmail.com \
    /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.