unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: George Clemmer <myglc2@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 33223@debbugs.gnu.org
Subject: bug#33223: In vm-image >>> 'guix package -i' >>> "-python-3.6.5.drv... -Killed"
Date: Thu, 01 Nov 2018 09:45:12 -0400	[thread overview]
Message-ID: <cuc4ld0syhj.fsf@gmail.com> (raw)
In-Reply-To: <CAE4v=pgWbeZy3gU3MvOy3ampLV_K7a4ZY1T8ydDbfyDAhgbKwA@mail.gmail.com>

Hello!

Gábor Boskovits <boskovits@gmail.com> writes:

> George Clemmer <myglc2@gmail.com> ezt írta (időpont: 2018. nov. 1., Cs, 3:11):
>>
>> In a 'guix system vm-image' VM produced using Guix from Git
>> v0.15.0-3097-gc16913d34

>> g1@sysi53 ~$ guix package -i emacs-no-x

>> building /gnu/store/phy1nbsmlml06lkjixjw2dfb4k6wi5al-python-3.6.5.drv...
>> -Killed

> I just came across this in a guix-help thread, there it seems that the
> VM does not have enough resources to build python3. Can that be the
> case here?

Thanks. The image was built by ...

guix system vm-image -M 4 -c 4 --image-size=20GB

... and run with 'qemu ... -m 5120'. Based on your comment I tried '-m
20G' and now the GiB Mem shown in top grows to 98.7/19.6, the VM
crashes, and there is no "Killed" message ;-O

Yes it's out of resources. But commit 7a06cdfa8 worked a day
earlier. Why is ...-python-3.6.5.drv... suddenly so hungry? Can Guix
infrastructure issues explain this?

- TIA, George

  reply	other threads:[~2018-11-01 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  2:09 bug#33223: In vm-image >>> 'guix package -i' >>> "-python-3.6.5.drv... -Killed" George Clemmer
2018-11-01  2:35 ` George Clemmer
2018-11-01  8:45 ` Gábor Boskovits
2018-11-01 13:45   ` George Clemmer [this message]
2018-11-01 14:44     ` Gábor Boskovits
2018-11-03 19:27     ` George Clemmer
2021-02-02 14:30       ` Maxim Cournoyer

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=cuc4ld0syhj.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=33223@debbugs.gnu.org \
    --cc=boskovits@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 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).