unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Attila Lendvai <attila@lendvai.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: shepherd: failing test: should `herd stop` stop a respawning process?
Date: Sat, 30 Nov 2024 19:29:26 +0100	[thread overview]
Message-ID: <87bjxwy3qx.fsf@gnu.org> (raw)
In-Reply-To: <wkZLkllEwNfE_0mHaxcu-Yk_KJ-f0Wv5aVHV8yZzsXdBxMrqSpYADJwXHKcXETnVvyjRioLT_wc8Pp7_tPn_-tEHhyS7ZgKpY-OpbsvndHM=@lendvai.name> (Attila Lendvai's message of "Fri, 22 Nov 2024 20:43:41 +0000")

Hi Attila,

Attila Lendvai <attila@lendvai.name> skribis:

> ok, i've attached a stipped down version of the test case. it hopefully reproduces the same situation i'm observing on my servers.
>
> which seems to be the following:
>
>   1. i have a service that keeps respawning (typically due to a config
>      mistake)
>
>   2. said service is upgraded/replaced in a `guix system reconfigure`
>
>   3. v1 of the service keeps respawning forever, and there's nothing i
>      can do to stop it at this point. `herd disable` operates on v2 of
>      the service, while some fiber, or some signal handler of v1 is
>      still in a respawn loop.

Thanks for the detailed bug report and test case.  It’s a pretty nasty
bug that you found here.

Commit 5fe594d593e6dcb19e23029bf3ff5f4a77a92523 should fix it.  Let me
know if you notice anything wrong!

Ludo’.


      reply	other threads:[~2024-11-30 18:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-06 17:02 shepherd: failing test: should `herd stop` stop a respawning process? Attila Lendvai
2024-10-06 17:31 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-10-23 20:03 ` Ludovic Courtès
2024-11-22 20:43   ` Attila Lendvai
2024-11-30 18:29     ` Ludovic Courtès [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

  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=87bjxwy3qx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=attila@lendvai.name \
    --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).