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
