From: Julien Lepiller <julien@lepiller.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 48963@debbugs.gnu.org
Subject: bug#48963: "guix build guix" halts after exhausting memory
Date: Fri, 18 Jun 2021 06:52:10 -0400 [thread overview]
Message-ID: <E61C5B68-6995-4CD3-B3A8-77B98FCC430F@lepiller.eu> (raw)
In-Reply-To: <87lf77h565.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
No, the _test_ failure is consistent. The build itself now always completes, which is much better that before.
Le 18 juin 2021 05:51:14 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hi,
>
>Julien Lepiller <julien@lepiller.eu> skribis:
>
>> Le Thu, 17 Jun 2021 09:58:09 -0400,
>> Julien Lepiller <julien@lepiller.eu> a écrit :
>>
>>> Hi Ludo,
>>>
>>> I tried your patch by creating a variant of the guix package. My
>>> first attempt was a failure because it's still using almost all my
>>> memory and I forgot to enable my swap. In the second attempt, the
>>> build phase succeeded, but the build failed during the test phase
>>> (test/inferior). I've started a new build hoping it's a
>>> non-deterministic failure.
>>
>> I'm afraid after testing 2 more times that the test failure is
>> happening consistently, at least of armhf.
>
>(The _build_ failure, right?)
>
>Have you been able to see how this affects max RSS?
>
>Does it go any further than without the patch?
>
>Thanks,
>Ludo’.
[-- Attachment #2: Type: text/html, Size: 1554 bytes --]
next prev parent reply other threads:[~2021-06-18 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 22:23 bug#48963: "guix build guix" halts after exhausting memory Julien Lepiller
2021-06-11 22:30 ` Julien Lepiller
2021-06-16 20:01 ` Ludovic Courtès
2021-06-17 13:58 ` Julien Lepiller
2021-06-17 22:17 ` Julien Lepiller
2021-06-18 9:51 ` Ludovic Courtès
2021-06-18 10:52 ` Julien Lepiller [this message]
2021-06-20 21:00 ` Ludovic Courtès
2021-06-21 11:05 ` Julien Lepiller
2021-06-23 21:43 ` 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=E61C5B68-6995-4CD3-B3A8-77B98FCC430F@lepiller.eu \
--to=julien@lepiller.eu \
--cc=48963@debbugs.gnu.org \
--cc=ludo@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.
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).