unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: "Daniel Schäfer" <git@danielschaefer.me>, guix-devel@gnu.org
Subject: Re: Fwd: Running individual system tests
Date: Sat, 19 Oct 2019 13:27:01 +0200	[thread overview]
Message-ID: <87bludx9fe.fsf@devup.no> (raw)
In-Reply-To: <7a1ea893-6ec0-5312-a013-cdc246a1e1e5@danielschaefer.me>

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

Hello Daniel,

Daniel Schäfer <git@danielschaefer.me> writes:

> I'm still trying to figure out, how to run a single Guix system test 
> without building the entirety of Guix.
> Does anybody do this? Has anybody written a Guix system test for 
> something not in Guix? Maybe a personal or work-related project.

You only have to build the entirety of Guix once.  Later invokations of
"make check-system" will re-use the compiled modules from the previous
"make" invokation, and only compile those that changed in the mean time.

Note that 'run-basic-test' also builds a derivation of your Guix
checkout to make it available in the VM.  I suspect this is what you are
referring to?

For out-of-tree tests, you can try to hack 'gnu/tests.scm' and
'build-aux/run-system-tests.scm' to your needs.

HTH!

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

  reply	other threads:[~2019-10-19 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e9c67f90-8c08-7019-1dbc-a4cd09704728@danielschaefer.me>
2019-10-19 10:06 ` Fwd: Running individual system tests Daniel Schäfer
2019-10-19 11:27   ` Marius Bakke [this message]
2019-10-19 17:35   ` Ricardo Wurmus
2019-10-21  6:43     ` Daniel Schäfer
2019-10-23 12:03       ` Daniel Schäfer
2019-10-23 13:04         ` Danny Milosavljevic
2019-10-23 16:02         ` Fwd: " Ricardo Wurmus
2019-10-25 20:28   ` 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=87bludx9fe.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=git@danielschaefer.me \
    --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).