From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Eric Bavier <ericbavier@centurylink.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: python-minimal compilation is breaking
Date: Tue, 6 Nov 2018 14:00:12 +0900 [thread overview]
Message-ID: <CANVeeZz1sZdv599HeOUp=gfTr+Ds=WZbKcuHagMm1pyHio=Z-w@mail.gmail.com> (raw)
In-Reply-To: <20181105203001.77e43fbb@centurylink.net>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
Hi,
I ran into the same problem on a very powerful machine. In my case the
congestion test was the problem. It finished by eating all of my 128Gb of
RAM.
This problem is known and fixed upstream by disabling the test. I submitted
a patch to disable it on our 3.6.5 version, but it will have to go to
core-updates if merged.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33186#26
Thanks,
Mathieu
Le mar. 6 nov. 2018 11:30, Eric Bavier <ericbavier@centurylink.net> a
écrit :
> On Thu, 1 Nov 2018 05:18:00 +0100 (CET)
> <znavko@tutanota.com> wrote:
>
> > Hello, Guix Help!
> > This is not working on Lenovo G50-30 everytime (already 3 times)
> >
> > # guix system reconfigure /etc/config.scm --substitute-urls=
> https://berlin.guixsd.org <https://berlin.guixsd.org>
> > building
> /gnu/store/6c4g38n9fhvnlk2vasn34mdd6nvpgx8m-python-minimal-3.6.5.drv...
> > -Killed
> >
> > While it is working:
> >
> > $ free -m
> > total used free shared buff/cache
> available
> > Mem: 1882 777 322 72
> 782 1031
> > Swap: 2168 143 2024
> >
> >
> > I think it lacks resources: cpu 2.1GHz, RAM 2 Gb. When it crashes PC
> stops on 15-20 seconds, mouse does not move, and then process is killed.
> > What to try?
> >
>
> I submitted this patch that I created while struggling with the same
> package: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33284
>
> Perhaps it might help you too?
>
> `~Eric
>
[-- Attachment #2: Type: text/html, Size: 2815 bytes --]
prev parent reply other threads:[~2018-11-06 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 4:18 python-minimal compilation is breaking znavko
2018-11-01 8:38 ` Gábor Boskovits
2018-11-06 2:30 ` Eric Bavier
2018-11-06 5:00 ` Mathieu Othacehe [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='CANVeeZz1sZdv599HeOUp=gfTr+Ds=WZbKcuHagMm1pyHio=Z-w@mail.gmail.com' \
--to=m.othacehe@gmail.com \
--cc=ericbavier@centurylink.net \
--cc=help-guix@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.
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).