all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Timo Wilken" <guix@twilken.net>
To: "Attila Lendvai" <attila@lendvai.name>
Cc: 67538@debbugs.gnu.org, 67230@debbugs.gnu.org,
	67839@debbugs.gnu.org, 65178@debbugs.gnu.org
Subject: bug#67230: Shepherd stops responding during "guix system reconfigure"
Date: Fri, 15 Dec 2023 21:33:15 +0100	[thread overview]
Message-ID: <CXP6VUA179NT.24MHZOOPR4XQN@lap.twilken.net> (raw)
In-Reply-To: <mnlkXTye7wOZNVq5cAf2dviIwfvb8APeTaM5rHUGoPKVlZz9l4VxGNAde8FbJIPf9yPYn0FRXSh0Vb5myA3E3407Us_echjM6SOWv6sE8jY=@lendvai.name>

On Fri Dec 15, 2023 at 8:47 PM CET, Attila Lendvai wrote:
> i think i have found the root cause of this, as documented here: https://issues.guix.gnu.org/67839
>
> that issue contains patches for shepherd to reproduce it in its test suite.

Thank you very much for this, Attila!

Are the patch in 67839 and/or your branch "attila" linked from there in a
state that I could test them locally? Would it be valuable to you if I ran a
patched Shepherd and sent logs and/or backtraces as I encountered them?




  reply	other threads:[~2023-12-15 20:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 21:37 bug#67538: Shepherd stops responding during "guix system reconfigure" Timo Wilken
2023-11-29 21:54 ` Attila Lendvai
2023-11-30 11:23   ` Attila Lendvai
2023-12-14 22:55     ` bug#67230: " Timo Wilken
2023-12-15 19:47       ` bug#65178: " Attila Lendvai
2023-12-15 20:33         ` Timo Wilken [this message]
2023-12-15 21:24           ` bug#67538: " Attila Lendvai
2023-12-19 23:00         ` bug#65419: [Shepherd] Non-responding service control fiber Ludovic Courtès
2023-11-30 12:55   ` bug#67538: Shepherd stops responding during "guix system reconfigure" Simon Streit
2023-11-29 22:56 ` Michal Atlas

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=CXP6VUA179NT.24MHZOOPR4XQN@lap.twilken.net \
    --to=guix@twilken.net \
    --cc=65178@debbugs.gnu.org \
    --cc=67230@debbugs.gnu.org \
    --cc=67538@debbugs.gnu.org \
    --cc=67839@debbugs.gnu.org \
    --cc=attila@lendvai.name \
    /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.