unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 2/2] system: Add btrfs file system support.
Date: Sat, 03 Dec 2016 16:21:58 +0100	[thread overview]
Message-ID: <877f7havhl.fsf@gnu.org> (raw)
In-Reply-To: <87zikeposs.fsf@gmail.com> (Chris Marusich's message of "Fri, 02 Dec 2016 03:12:51 -0800")

Chris Marusich <cmmarusich@gmail.com> skribis:

> David Craven <david@craven.ch> writes:
>
>> Ludo: Is there any way we can speed up the installer system tests? :)
>
> I've also wondered about this.  I'm not sure how long each test takes to
> run, so an analysis of the tests to find their slow areas might help
> guide us.  I suspect that we could probably speed up the tests by using
> a shared test fixture of some kind (e.g., a common store, or a base qemu
> disk image [1], which could be used by multiple tests), but first we'd
> need to know which part(s) are slow.

Tests that use ‘system-qemu-image/shared-store-script’ (basic, mcron,
openssh, etc.) are relatively fast.

However, the installation tests have to use a real (full, standalone)
image for the installation disk, and also for the target disk.
Otherwise we wouldn’t be testing the same thing.

> Another possibility might be to parallelize the tests (I don't think the
> system tests are done in parallel right now, even if you specify "make
> -j", but someone correct me if I'm wrong), but that could be
> counter-productive if it took up too many system resources.

They are derivation builds, so they are performed in parallel according
to --max-jobs.

Thanks,
Ludo’.

  parent reply	other threads:[~2016-12-03 15:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 18:36 [PATCH 1/2] gnu: Add btrfs-progs/static David Craven
2016-11-30 18:36 ` [PATCH 2/2] system: Add btrfs file system support David Craven
2016-12-01 19:18   ` Marius Bakke
2016-12-02 10:50     ` David Craven
2016-12-02 11:12       ` Chris Marusich
2016-12-02 16:27         ` David Craven
2016-12-03 15:21         ` Ludovic Courtès [this message]
2016-12-03 15:18       ` Ludovic Courtès
2016-12-03 15:31   ` Ludovic Courtès
2016-12-03 16:21     ` David Craven
2016-12-05 20:44       ` Ludovic Courtès
2016-12-03 15:15 ` [PATCH 1/2] gnu: Add btrfs-progs/static Ludovic Courtès
2016-12-03 21:41   ` David Craven
2016-12-05 20:51     ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877f7havhl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).