From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 59784@debbugs.gnu.org
Subject: bug#59784: [version 1.4.0rc1] Retrying a failed install fails
Date: Fri, 16 Dec 2022 17:57:12 +0100 [thread overview]
Message-ID: <87pmcji8wn.fsf@gnu.org> (raw)
In-Reply-To: <87v8mcz9ai.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Thu, 15 Dec 2022 21:44:37 +0100")
Hi,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> Desperately I tried also adding fsync, to no avail, both issues remain.
> Non-working patch attached.
>
> Maybe dynamic-wind is an inappropriate pattern here?
>
> If I interrupt installation using Ctrl-C (which I normally don’t,
> instead I unplug Ethernet), then I have to press Ctrl-C twice. Maybe
> that could be related to why I need to resume twice?
One finding: when hitting C-c, the dynamic-wind exit handler (the one
that restores the database and umounts the cow store) is *not* executed.
This is because ‘call-with-mnt-container’ sets a SIGINT handler that
terminates that process with SIGKILL (I’m not entirely sure of the
rationale, but said process cannot handle signals in Scheme while it’s
in ‘waitpid’, called from ‘run-command’).
I did reproduce the issue in a VM by running “ifconfig ens3 down” in a
tty, or by killing the ‘guix substitute’ process, to cause failure of
‘guix system init’. In that case the database is indeed restored, but I
occasionally get errors like “/gnu/store/….drv: No such file or
directory”.
Ludo’.
next prev parent reply other threads:[~2022-12-16 16:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 17:52 bug#59784: [version 1.4.0rc1] Retrying a failed install fails pelzflorian (Florian Pelz)
2022-12-09 9:42 ` Ludovic Courtès
2022-12-09 11:11 ` Ludovic Courtès
2022-12-10 8:39 ` pelzflorian (Florian Pelz)
2022-12-13 9:40 ` Ludovic Courtès
2022-12-13 9:48 ` Ludovic Courtès
2022-12-13 22:22 ` pelzflorian (Florian Pelz)
2022-12-13 23:16 ` Ludovic Courtès
2022-12-14 13:36 ` pelzflorian (Florian Pelz)
2022-12-14 21:47 ` pelzflorian (Florian Pelz)
2022-12-14 23:50 ` Ludovic Courtès
2022-12-15 17:46 ` pelzflorian (Florian Pelz)
2022-12-15 20:44 ` pelzflorian (Florian Pelz)
2022-12-16 16:57 ` Ludovic Courtès [this message]
2022-12-16 20:28 ` pelzflorian (Florian Pelz)
2022-12-17 11:01 ` Ludovic Courtès
2022-12-17 19:36 ` pelzflorian (Florian Pelz)
2022-12-17 16:15 ` Ludovic Courtès
2022-12-17 19:27 ` pelzflorian (Florian Pelz)
2022-12-17 21:30 ` Ludovic Courtès
2022-12-18 0:23 ` Ludovic Courtès
2022-12-16 13:55 ` Maxime Devos
2022-12-16 20:17 ` pelzflorian (Florian Pelz)
2022-12-18 16:41 ` pelzflorian (Florian Pelz)
2022-12-12 12:07 ` pelzflorian (Florian Pelz)
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=87pmcji8wn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59784@debbugs.gnu.org \
--cc=othacehe@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.