unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Léon Lain Delysid" <leon.lain.delysid@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 41710@debbugs.gnu.org
Subject: bug#41710: Possibly found a bug while doing a "guix pull"
Date: Sun, 7 Jun 2020 03:15:41 +0200	[thread overview]
Message-ID: <CAHecTjfDLmc0CrYfi__VqkRVYjwtLRj5fTRPSSGioO2qbqFrDA@mail.gmail.com> (raw)
In-Reply-To: <DE1A9277-D737-45E4-908A-A63E6DF6BE1F@lepiller.eu>


[-- Attachment #1.1: Type: text/plain, Size: 1920 bytes --]

Hello,
Sorry for responding so late, I was busy otherwise.
I have more than enough RAM, 16 GB. And also lots of swap space. And my
/tmp takes 104KB of space.



[image: Screenshot from 2020-06-07 03-05-33.jpg]

On Thu, Jun 4, 2020 at 5:41 PM Julien Lepiller <julien@lepiller.eu> wrote:

> Le 4 juin 2020 10:38:09 GMT-04:00, "Léon Lain Delysid" <
> leon.lain.delysid@gmail.com> a écrit :
> >Hello!
> >I just tried to "guix pull" on my Debian Buster GNU/Linux system. Twice
> >it
> >made the system completely freeze for a few seconds and then reboot.
> >And
> >that third time it didn't crash the system but the guix pull failed and
> >returned this error:
> >https://pastebin.com/vhDR8gDC
> >
> >Can somebody help me please?
> >
> >(Before doing the third "pull", I did an "apt update" and "upgrade",
> >but I
> >wasn't that much behind in updates, I had done it less than a week ago
> >last. My last "guix pull" was made at the same time as the "apt
> >update", a
> >few days ago.)
> >
> >Hoping I can resolve this soon or that my feedback was positive for the
> >development of Guix. =)
> >I can provide log debug info (if there is any) upon request.
> >
> >Best regards!
>
> Sorry pastebin is not tor friendly, I couldn't look at it.
>
> For the freezing part, could it be that you have relatively low free ram
> (<2GB) and no swap? Or maybe /tmp is mounted as a tmpfs and for some reason
> it takes a lot of space?
>
> You might need to use substitutes when runnning guix pull. I don't have
> that much ram either on some computers, so I always take a look at
> https://ci.guix.gnu.org/jobset/guix-modular-master and choose the latest
> commit that was built for my architeeture. Then eg. guix pull
> --commit=c987b72
>
> This will allow guix to download substitutes for guix pull instead of
> building locally, which doesn't require any ram usage.
>
> HTH!
>

[-- Attachment #1.2: Type: text/html, Size: 2778 bytes --]

[-- Attachment #2: Screenshot from 2020-06-07 03-05-33.jpg --]
[-- Type: image/jpeg, Size: 942993 bytes --]

      parent reply	other threads:[~2020-06-07  2:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 14:38 bug#41710: Possibly found a bug while doing a "guix pull" Léon Lain Delysid
2020-06-04 15:41 ` Julien Lepiller
2020-06-04 18:11   ` zimoun
2020-06-06 13:22     ` Ludovic Courtès
2020-06-07  1:12       ` Léon Lain Delysid
2020-06-07 20:06         ` Ludovic Courtès
2020-06-07 23:15           ` Léon Lain Delysid
2020-06-08 11:02             ` Danny Milosavljevic
2020-06-10 13:25               ` Ludovic Courtès
2020-06-12  9:55                 ` Léon Lain Delysid
2020-06-07  1:19     ` Léon Lain Delysid
2020-06-07  1:15   ` Léon Lain Delysid [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=CAHecTjfDLmc0CrYfi__VqkRVYjwtLRj5fTRPSSGioO2qbqFrDA@mail.gmail.com \
    --to=leon.lain.delysid@gmail.com \
    --cc=41710@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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).