unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 32955@debbugs.gnu.org
Subject: bug#32955: Cuirass: Some tests depend on 'guix-current', which makes them resource expensive
Date: Mon, 08 Oct 2018 15:25:46 +0200	[thread overview]
Message-ID: <87ftxgzi1x.fsf@gnu.org> (raw)
In-Reply-To: <87murr5foj.fsf@lassieur.org> ("Clément Lassieur"'s message of "Sat, 06 Oct 2018 16:10:36 +0200")

Hello,

Clément Lassieur <clement@lassieur.org> skribis:

> Tests depending on 'guix-current' are expensive in terms of CPU and
> storage usage since we need to build (current-guix) and then store a
> couple of full system images.

[...]

> Is there another way to get those tests to work without depending on
> 'guix-current'?

These tests are indeed expensive.  However the motivation here is
precisely to test a complete installation procedure using the current
Guix in the installation image.  If we were to change that we’d be
testing something different and much less interesting.

So I think there’s not much we can do here.

Does that make sense?

(Note that all the other system tests use just whatever snapshot the
‘guix’ package refers to, which is good enough for them because they
don’t test things where Guix itself is involved.)

Thanks,
Ludo’.

  parent reply	other threads:[~2018-10-08 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 14:10 bug#32955: Cuirass: Some tests depend on 'guix-current', which makes them resource expensive Clément Lassieur
2018-10-06 14:37 ` Clément Lassieur
2018-10-07 12:16   ` Clément Lassieur
2018-10-08 13:25 ` Ludovic Courtès [this message]
2018-10-08 13:44   ` Clément Lassieur

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=87ftxgzi1x.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32955@debbugs.gnu.org \
    --cc=clement@lassieur.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).