all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>, guix-devel@gnu.org
Subject: Re: New file "tests/docker-inception.scm" with small problem
Date: Fri, 11 Jan 2019 23:06:20 +0100	[thread overview]
Message-ID: <87ef9i7stf.fsf@fastmail.com> (raw)
In-Reply-To: <20190111171719.3114e712@scratchpost.org>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Danny Milosavljevic <dannym@scratchpost.org> writes:

> Hi,
>
> there's a new branch "wip-docker-test" which has a new (non-system) test tests/docker-inception.scm .
>
> You can run it via:
>
>   make TESTS=tests/docker-inception.scm check
>
> Unfortunately, it fails with some inscrutable qemu error message:
>
> qemu-system-x86_64: -virtfs local,path=/home/dannym/src/guix-ns14/guix/test-tmp/store,security_model=none,mount_tag=TAGy5ajggutlpmxibmqfchkokzxuwid: cannot ini
> tialize fsdev 'TAGy5ajggutlpmxibmqfchkokzxuwid': failed to open '/home/dannym/src/guix-ns14/guix/test-tmp/store': No such file or directory
>
> Trying to fix it (setting NIX_STORE etc) made it worse, so I reverted that part.
>
> Help?

I don't know what the problem is, but the test reads an awful lot like a
"system test" to me.  Any particular reason you wish to run this as a
"unit test"?  Perhaps we need another category for "package tests"?  :)

I suspect converting to a system test will fix this problem, as it will
use a "normal" store instead of the scratch one in ./test-tmp.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2019-01-11 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 16:17 New file "tests/docker-inception.scm" with small problem Danny Milosavljevic
2019-01-11 22:06 ` Marius Bakke [this message]

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=87ef9i7stf.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=dannym@scratchpost.org \
    --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 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.