From: Maxime Devos <maximedevos@telenet.be>
To: Josselin Poiret <dev@jpoiret.xyz>,
Holden Green <holdenmgreen@gmail.com>,
55059@debbugs.gnu.org
Subject: bug#55059: bug in `guix pull`
Date: Sun, 24 Apr 2022 10:21:42 +0200 [thread overview]
Message-ID: <e06f9c25a3ddce83c39a18bc296b082c8cced884.camel@telenet.be> (raw)
In-Reply-To: <87h76j3ptn.fsf@jpoiret.xyz>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
Josselin Poiret via Bug reports for GNU Guix schreef op zo 24-04-2022
om 09:25 [+0200]:
> > Computing Guix derivation for 'x86_64-linux'... /guix pull: error:
> > You
> > found a bug: the program
> > '/gnu/store/lb30npcazqfbw8cbkk9kf8pcf17c2sl6-compute-guix-
> > derivation'
> > failed to compute the derivation for Guix (version:
> > "eb34ff16cc9038880e87e1a58a93331fca37ad92"; system: "x86_64-linux";
> > host version: "1.3.0-1.771b866"; pull-version: 1).
> > Please report the COMPLETE output above by email to <
> > bug-guix@gnu.org>.
>
> How much RAM does your machine have? The derivation computation
> famously takes quite a bit of memory. If that's the issue, you
> could add some swap space.
If <https://issues.guix.gnu.org/50238> was applied, we wouldn't have to
guess what is the cause, instead "guix pull" would just tell us if it's
a networking error or a stack overflow or an oom(*) ...
(*) Except on Linux due to overcommit, though that could be worked-
around by setting the appropriate variable in /proc/sys or by doing
'setrlimit' like some of Guile's OOM tests do.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-04-24 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 23:42 bug#55059: bug in `guix pull` Holden Green
2022-04-24 7:25 ` Josselin Poiret via Bug reports for GNU Guix
2022-04-24 8:21 ` Maxime Devos [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e06f9c25a3ddce83c39a18bc296b082c8cced884.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55059@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=holdenmgreen@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.