all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: Vladilen Kozin <vladilen.kozin@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: shepherd service works on host but fails inside system container
Date: Mon, 27 Mar 2023 08:39:22 +0000	[thread overview]
Message-ID: <GMf-TBxb4I1IQNrAIYfbruABW-nyzCTMaMQisGXaMN0VtGVGYV_SpkuP0Y4mBMwZ6qKgOrktbRvj91rgDdKITN7ZPbAhVmwFpJxhuuxAQ88=@lendvai.name> (raw)
In-Reply-To: <CACw=CXMTsMa6D+rAHW+KvATOje4cGqkR_yQJx9qDYfSa9CFfgw@mail.gmail.com>

> Relatedly, does anyone have a nicer workflow they use to define and
> test shepherd services?

i'm not sure it's a nicer workflow, but i'm mimicing the Guix tests:

https://github.com/attila-lendvai/guix-crypto/blob/main/tests/swarm-tests.scm#L19

it is based on `guix system vm` and the testing is by manually looking at stuff in the VM (you get a VM console in your terminal). the startup time is in the ballpark of 20-30 secs on my laptop.

adding automated tests to this is i think possible.

let us know if you have a faster cycle.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Since no individual acting separately can lawfully use force to destroy the rights of others, does it not logically follow that the same principle also applies to the common force that is nothing more than the organized combination of the individual forces?”
	— Frédéric Bastiat (1801–1850), 'The Law' (1850)



      parent reply	other threads:[~2023-03-27  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 10:20 shepherd service works on host but fails inside system container Vladilen Kozin
2023-03-22 12:14 ` Vladilen Kozin
2023-03-22 13:11   ` Vladilen Kozin
2023-03-27  8:39 ` Attila Lendvai [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='GMf-TBxb4I1IQNrAIYfbruABW-nyzCTMaMQisGXaMN0VtGVGYV_SpkuP0Y4mBMwZ6qKgOrktbRvj91rgDdKITN7ZPbAhVmwFpJxhuuxAQ88=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=vladilen.kozin@gmail.com \
    /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.