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

Hi,

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.

They are built at each evaluation because they depend on 'guix-current'.
(And they all fail.)

    test.btrfs-root-os.x86_64-linux
    test.encrypted-root-os.x86_64-linux
    test.installed-extlinux-os.x86_64-linux
    test.separate-home-os.x86_64-linux
    test.raid-root-os.x86_64-linux
    test.separate-store-os.x86_64-linux
    test.iso-image-installer.x86_64-linux
    test.installed-os.x86_64-linux
    
    test.btrfs-root-os.i686-linux
    test.encrypted-root-os.i686-linux
    test.installed-extlinux-os.i686-linux
    test.separate-home-os.i686-linux
    test.raid-root-os.i686-linux
    test.separate-store-os.i686-linux
    test.iso-image-installer.i686-linux
    test.installed-os.i686-linux

It seems that the reason is explained by that comment in
gnu/tests/install.scm:

    ;; Since the image has no network access, use the
    ;; current Guix so the store items we need are in
    ;; the image and add packages provided.

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

Clément

             reply	other threads:[~2018-10-06 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 14:10 Clément Lassieur [this message]
2018-10-06 14:37 ` bug#32955: Cuirass: Some tests depend on 'guix-current', which makes them resource expensive Clément Lassieur
2018-10-07 12:16   ` Clément Lassieur
2018-10-08 13:25 ` Ludovic Courtès
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=87murr5foj.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=32955@debbugs.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).