From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36162@debbugs.gnu.org
Subject: [bug#36162] [PATCH 0/4] Add 'remote-eval'
Date: Wed, 12 Jun 2019 11:43:21 -0400 [thread overview]
Message-ID: <87r27ybyhy.fsf@sdf.lonestar.org> (raw)
In-Reply-To: <87k1dqvrlh.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 12 Jun 2019 15:52:10 +0200")
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Tests are supposed to be deterministic, so as such, it makes sense for
> tests to be normal derivations, as is currently the case.
Makes sense. I actually hadn't realized that the Guix test suite (those
run with 'check' rather than 'check-system') were also derivations until
you mentioned it. It seems like looking at the implementation there
would give me a better idea of how to structure my tests.
> In that spirit, we should instead tweak <virtual-machine> so that we
> can instruct it to build an autonomous VM with its own store.
I like that idea. There's a 'system-qemu-image/shared-store-script', but
no 'system-qemu-image-script', so I'll have to take what I did for my
test suite experiments and turn it into something proper.
> OTOH, we could also have ‘container-eval’, similar to ‘remote-eval’,
> which would be useful for effectful code, such as code that needs to
> interact with the daemon. Food for thought!
'container' in the sense of 'guix environment' containers?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-06-12 15:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 0:42 Progress on 'guix deploy' Jakob L. Kreuze
2019-06-09 2:19 ` Christopher Lemmer Webber
2019-06-10 9:31 ` Ludovic Courtès
2019-06-10 17:47 ` Jakob L. Kreuze
2019-06-11 0:35 ` [bug#36162] [PATCH 0/4] Add 'remote-eval' Jakob L. Kreuze
2019-06-12 13:52 ` Ludovic Courtès
2019-06-12 15:43 ` Jakob L. Kreuze [this message]
2019-06-12 20:39 ` Ludovic Courtès
2019-06-11 15:14 ` Progress on 'guix deploy' Jakob L. Kreuze
2019-06-11 18:40 ` Ludovic Courtès
2019-06-11 20:54 ` Jakob L. Kreuze
2019-06-12 16:34 ` Jakob L. Kreuze
2019-06-11 18:36 ` Ludovic Courtès
2019-06-11 19:42 ` Jakob L. Kreuze
-- strict thread matches above, loose matches on Subject: below --
2019-06-10 21:08 [bug#36162] [PATCH 0/4] Add 'remote-eval' Ludovic Courtès
2019-06-11 13:26 ` Ricardo Wurmus
2019-06-11 17:35 ` Jakob L. Kreuze
2019-06-12 13:45 ` Ludovic Courtès
2019-06-12 15:12 ` Jakob L. Kreuze
2019-06-13 11:09 ` Ludovic Courtès
2019-06-13 13:18 ` Jakob L. Kreuze
2019-06-13 16:17 ` Jakob L. Kreuze
2019-06-14 11:20 ` Ludovic Courtès
2019-06-30 13:24 ` Christopher Lemmer Webber
2019-07-04 16:22 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r27ybyhy.fsf@sdf.lonestar.org \
--to=zerodaysfordays@sdf.lonestar.org \
--cc=36162@debbugs.gnu.org \
--cc=ludo@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.