unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
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 21:28:29 +0100	[thread overview]
Message-ID: <871qoz855e.fsf@pelzflorian.de> (raw)
In-Reply-To: <87pmcji8wn.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 16 Dec 2022 17:57:12 +0100")

Ludovic Courtès <ludo@gnu.org> writes:
> 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.

Impressive findings.

Now that you found the dynamic-wind’s out-guard does not even run: Uhh I
had misdiagnosed when I thought your 'stop-service' patch had made a
difference and caused a second resume to work.  Second resume was
already possible on rc2.  Except eventually resume stops working and on
some install attempts with rc2, resume stops working right away.

After seeing that you opened a bug#60116 on setsid(), I tested removing
the setsid call and it had no effect, but if the dynamic-wind’s
out-guard does not even run, that is to be expected.


> 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”.

Yes, this is the error message that I get on failing resumes.

Regards,
Florian




  reply	other threads:[~2022-12-16 20:29 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
2022-12-16 20:28                         ` pelzflorian (Florian Pelz) [this message]
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

  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=871qoz855e.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=59784@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=othacehe@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).