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: Mon, 10 Jun 2019 20:35:52 -0400 [thread overview]
Message-ID: <87k1dtj6vr.fsf_-_@sdf.lonestar.org> (raw)
In-Reply-To: <871s01l4c2.fsf@sdf.lonestar.org> (Jakob L. Kreuze's message of "Mon, 10 Jun 2019 13:47:57 -0400")
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
Wow, this is great! It seems like this patch series is implementing a
number of things I'd been wishing I could just import from some other
Guix module. I'm signing off for the night, but I'll apply this tomorrow
and give you some feedback.
Ludovic Courtès <ludo@gnu.org> writes:
> There are no tests for ‘remote-eval’ currently. It would need a VM
> with access to the store, as Jakob explained on guix-devel.
One idea I had in developing my test suite was to design another record
type to supplement '<system-test>' for tests that /do/ need access the
host's store as they're running, but thought it would be too intrusive
as it would only be used by the tests for '(gnu machine)'. Now that we
have a ‘remote-eval’ that would benefit from being tested that way,
though, I'd like to ask: is that something I should look into?
Thanks again for implementing this
Jakob
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next parent reply other threads:[~2019-06-11 0:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875zpgrjqf.fsf@sdf.lonestar.org>
[not found] ` <87h88x7pni.fsf@gnu.org>
[not found] ` <871s01l4c2.fsf@sdf.lonestar.org>
2019-06-11 0:35 ` Jakob L. Kreuze [this message]
2019-06-12 13:52 ` [bug#36162] [PATCH 0/4] Add 'remote-eval' Ludovic Courtès
2019-06-12 15:43 ` Jakob L. Kreuze
2019-06-12 20:39 ` Ludovic Courtès
2019-06-10 21:08 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
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=87k1dtj6vr.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 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).