unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: "Léon Lain Delysid" <leon.lain.delysid@gmail.com>, 42002@debbugs.gnu.org
Subject: bug#42002: Bug: Signal kill during build
Date: Mon, 22 Jun 2020 09:51:44 -0400	[thread overview]
Message-ID: <20200622135144.GA9358@jasmine.lan> (raw)
In-Reply-To: <20200622124708.GC22974@E5400>

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

On Mon, Jun 22, 2020 at 03:47:08PM +0300, Efraim Flashner wrote:
> The signal 9 (killed) makes me think a C++ program killed. I checked
> wikipedia and it says the Banana Pi M3 has 2GB of RAM. Was there
> anything else running at the time? 'guix pull' can be resource
> intensive, especially on lower powered machines.

I think it should be possible with 2GB of RAM, if you limit the number
of concurrent builds.

For example, something like `guix pull --max-jobs=1`.

And I think the memory requirements should decrease with the recently
released Guile 3.0.3:

https://lists.gnu.org/archive/html/guile-devel/2020-06/msg00008.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-06-22 13:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 12:28 bug#42002: Bug: Signal kill during build Léon Lain Delysid
2020-06-22 12:47 ` Efraim Flashner
2020-06-22 12:53   ` Léon Lain Delysid
2020-06-23  0:38     ` Bonface M. K.
2020-06-23  5:57       ` Efraim Flashner
2020-06-23 14:03         ` Bengt Richter
2022-07-14  3:23         ` bug#42002: 'guix pull' build processes get SIGKILL on ARMv7 Maxim Cournoyer
2020-06-22 13:51   ` Leo Famulari [this message]
2020-06-23 21:26     ` bug#42002: Bug: Signal kill during build Ludovic Courtès

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=20200622135144.GA9358@jasmine.lan \
    --to=leo@famulari.name \
    --cc=42002@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=leon.lain.delysid@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).