From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 38167@debbugs.gnu.org
Subject: bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes
Date: Tue, 31 Dec 2019 19:18:13 +0100 [thread overview]
Message-ID: <87fth0xst6.fsf@gnu.org> (raw)
In-Reply-To: <20191231164450.26450360@scratchpost.org> (Danny Milosavljevic's message of "Tue, 31 Dec 2019 16:44:50 +0100")
Hi,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Sun, 29 Dec 2019 23:41:42 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> > It could be because my modules in GUIX_PACKAGE_PATH contain an import cycle
>> > (I don't know whether it does, but I had such a cycle before).
>>
>> And that’s definitely a possibility! Can you try unsetting
>> GUIX_PACKAGE_PATH?
>
> Sure, but that will not decide it conclusively.
>
> It's pretty rare that guix pull has the problem above (once a week or so), so
> it could also be that it will work because it got a non-problematic case the
> same time (but not because of) I unset GUIX_PACKAGE_PATH.
If you can reproduce the bug when GUIX_PACKAGE_PATH is unset, I’m happy
to investigate further. Otherwise it’s hard to conclude because we’re
effectively running arbitrary code so the bug may well have nothing to
do with ‘guix pull’ itself.
Let me know!
Ludo’.
next prev parent reply other threads:[~2019-12-31 18:19 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 [this message]
2020-01-01 12:51 ` Danny Milosavljevic
2020-10-09 2:11 ` Maxim Cournoyer
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=87fth0xst6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38167@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).