From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#28111: qemu testsuite fails
Date: Thu, 18 Jan 2018 18:03:33 +0100
Message-ID: <87o9lr6qvu.fsf@gnu.org>
References: <20170816185317.3udxvtcclqkoqwkx@abyayala>
	<20170816193516.gb624goutduaj4rn@abyayala> <87bmhsi6ig.fsf@gnu.org>
	<873734hul6.fsf@gnu.org> <87wp0fa20f.fsf@gnu.org>
	<87tvvjtjau.fsf@gnu.org> <87607z6u5m.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36925)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ecDbj-0008Ga-Ct
	for bug-guix@gnu.org; Thu, 18 Jan 2018 12:04:08 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ecDbe-00081b-7x
	for bug-guix@gnu.org; Thu, 18 Jan 2018 12:04:07 -0500
Received: from debbugs.gnu.org ([208.118.235.43]:53940)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1ecDbe-000813-5N
	for bug-guix@gnu.org; Thu, 18 Jan 2018 12:04:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ecDbd-00041Y-Jc
	for bug-guix@gnu.org; Thu, 18 Jan 2018 12:04:01 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.28111.B28111.151629501915438@debbugs.gnu.org>
In-Reply-To: <87607z6u5m.fsf@gnu.org> (Mathieu Lirzin's message of "Thu, 18
	Jan 2018 16:52:53 +0100")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: 28111@debbugs.gnu.org

Mathieu Lirzin <mthl@gnu.org> skribis:

> Mathieu Lirzin <mthl@gnu.org> writes:
>
>> ludo@gnu.org (Ludovic Court=C3=A8s) writes:
>>
>>> Mathieu Lirzin <mthl@gnu.org> skribis:
>>>
>>>> My previous snippet didn't include the actual error
>>>>
>>>> TEST: tests/test-hmp... (pid=3D27743)
>>>>   /arm/hmp/integratorcp:                                              =
 OK
>>>>   /arm/hmp/nuri:                                                      =
 qemu-system-arm: cannot set up guest memory 'exynos4210.dram0': Cannot all=
ocate memory
>>>> Broken pipe
>>>> FAIL
>>>> GTester: last random seed: R02S53adf2b44f1ff46cb48bd55ebce8854c
>>>> (pid=3D27751)
>>>>   /arm/hmp/mps2-an511:                                                =
 OK
>>>>   /arm/hmp/verdex:                                                    =
 OK
>>>>   /arm/hmp/ast2500-evb:                                               =
 OK
>>>>   /arm/hmp/smdkc210:                                                  =
 qemu-system-arm: cannot set up guest memory 'exynos4210.dram0': Cannot all=
ocate memory
>>>> Broken pipe
>>>> FAIL
>>>>
>>>> I have tried to build QEMU again with the same guix version and succee=
d.
>>>> So Like previously reported this is underterministic.
>>>
>>> Could the initial error be the result of insufficient memory?
>>
>> Maybe.  I don't recall if I was doing something memory intensive while
>> compiling.  Given that I have 8Gb of RAM and that, QEMU test suite seems
>> quite greedy.
>
> Ohh I think the memory issue might be related to the fact I running the
> commands from Emacs shell-mode.  I have encoutered a memory issue with
> Emacs when running =E2=80=98guix system build=E2=80=99.  After the compil=
ation process
> stopped Emacs was still using more than 5Gb of RAM.

Oh yes, that could definitely be the culprit.  :-/

I guess we can close this bug and reopen it if this diagnosis turned out
to be wrong.

Ludo=E2=80=99.