From: Simon Tournier <zimon.toutoune@gmail.com>
To: Zack Weinberg <zack@owlfolio.org>, 72340@debbugs.gnu.org
Subject: bug#72340: guix should not ask me to report a bug if it fails due to running out of memory
Date: Tue, 03 Sep 2024 16:39:27 +0200 [thread overview]
Message-ID: <87ed60u7hc.fsf@gmail.com> (raw)
In-Reply-To: <8f273f8d-50db-463b-a0c1-cff561661f7e@app.fastmail.com>
Hi,
On Sun, 28 Jul 2024 at 16:02, "Zack Weinberg" via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
> Computing Guix derivation for 'x86_64-linux'... \
> GC Warning: Failed to expand heap by 8388608 bytes
> [previous line repeats 79 more times]
> GC Warning: Failed to expand heap by 69632 bytes
> GC Warning: Out of Memory! Heap size: 402 MiB. Returning NULL!
> Warning: Unwind-only out of memory exception; skipping pre-unwind handler.
> guix pull: error: You found a bug: the program
> '/gnu/store/6pckga173mjbpfz7a2bl93h4gimd8fp5-compute-guix-derivation'
> failed to compute the derivation for Guix (version:
> "46a64c7fdd057283063aae6df058579bb07c4b6a"; system: "x86_64-linux";
> host version: "e4aabf42b33346849cb565199cfafc49d4f0aeff";
I guess this bug had been fixed since then. Do you still have it?
Aside, I am not able to reproduce it:
guix time-machine -q --commit=e4aabf42b33346849cb565199cfafc49d4f0aeff \
-- time-machine -q --commit=46a64c7fdd057283063aae6df058579bb07c4b6a \
-- describe
This passes for me.
Cheers,
simon
next prev parent reply other threads:[~2024-09-03 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 16:02 bug#72340: guix should not ask me to report a bug if it fails due to running out of memory Zack Weinberg via Bug reports for GNU Guix
2024-09-03 14:39 ` Simon Tournier [this message]
2024-09-03 15:30 ` Zack Weinberg via Bug reports for GNU Guix
2024-09-03 16:09 ` Simon Tournier
2024-09-03 18:23 ` Zack Weinberg via Bug reports for GNU Guix
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=87ed60u7hc.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=72340@debbugs.gnu.org \
--cc=zack@owlfolio.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).