unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 38167-done@debbugs.gnu.org
Subject: bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes
Date: Thu, 08 Oct 2020 22:11:20 -0400	[thread overview]
Message-ID: <87sgaorvw7.fsf@gmail.com> (raw)
In-Reply-To: <20200101135145.0ba23594@scratchpost.org> (Danny Milosavljevic's message of "Wed, 1 Jan 2020 13:51:45 +0100")

Hello,

Danny Milosavljevic <dannym@scratchpost.org> writes:

> Hi Ludo,
>
> okay, I've now (permanently) unset GUIX_PACKAGE_PATH and killed the problematic "guix pull" process.
>
> I run "guix pull" regularily.  Let's see what happens...

The 40 weeks of time that have passed since suggest the problem is now
gone :-).

Closing, but feel free to reopen if the problem persists with
GUIX_PACKAGE_PATH unset.

Thanks,

Maxim




  reply	other threads:[~2020-10-09  2:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11  7:06 bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes Danny Milosavljevic
2019-11-11  7:37 ` Christopher Baines
2019-11-11 20:42   ` Ludovic Courtès
2019-12-26 19:45     ` Danny Milosavljevic
2019-12-26 19:48       ` Danny Milosavljevic
2019-12-27 18:11         ` Ludovic Courtès
2019-12-28 11:01           ` Danny Milosavljevic
2019-12-28 14:52             ` Ludovic Courtès
2019-12-28 17:55               ` Danny Milosavljevic
2019-12-29 22:41                 ` Ludovic Courtès
2019-12-31 15:44                   ` Danny Milosavljevic
2019-12-31 18:18                     ` Ludovic Courtès
2020-01-01 12:51                       ` Danny Milosavljevic
2020-10-09  2:11                         ` Maxim Cournoyer [this message]
2019-12-27 18:08       ` Ludovic Courtès
2019-12-28 10:56         ` Danny Milosavljevic

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=87sgaorvw7.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=38167-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).