all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ahmad Draidi <ar2000jp@gmail.com>
Cc: 53998@debbugs.gnu.org
Subject: bug#53998: Guix pull always gets stuck at ~80% on fresh i686 1.3.0 install
Date: Sun, 27 Feb 2022 22:41:55 +0100	[thread overview]
Message-ID: <87fso4t2ak.fsf@gnu.org> (raw)
In-Reply-To: <417d2ede-f783-1fff-76de-11a24e56c617@gmail.com> (Ahmad Draidi's message of "Sun, 27 Feb 2022 17:20:58 +0400")

Hi Ahmad,

Ahmad Draidi <ar2000jp@gmail.com> skribis:

> I tested a few more times using the same method (clean install, etc)
> and the results were like this:
>
> - Pull seg faulted, 2nd pull worked
>
> - Pull seg faulted, 2nd pull got stuck
>
> - Pull finished without issues
>
> - Pull finished without issues
>
> - Pull seg faulted, 2nd pull worked
>
> - Pull finished without issues
>
> - Pull seg faulted (log attached), 2nd pull worked, system reconfigure
>   worked, reboot then pull again worked
>
>
> It's a bit random now, but at least it passes sometimes.

That doesn’t sound great.

How much (v)RAM does this (virtual) machine have?

Thanks for testing and reporting back,
Ludo’.




  reply	other threads:[~2022-02-27 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 16:16 bug#53998: Guix pull always gets stuck at ~80% on fresh i686 1.3.0 install Ahmad Draidi
2022-02-15 18:56 ` Leo Famulari
2022-02-16 14:58   ` Ludovic Courtès
2022-02-23 15:17     ` Ahmad Draidi
2022-02-27 13:20       ` Ahmad Draidi
2022-02-27 21:41         ` Ludovic Courtès [this message]
2022-03-01  8:33           ` Ahmad Draidi

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=87fso4t2ak.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53998@debbugs.gnu.org \
    --cc=ar2000jp@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.