From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: Mathieu Lirzin <mthl@gnu.org>, 28111-done@debbugs.gnu.org
Subject: bug#28111: qemu testsuite fails
Date: Sat, 19 Sep 2020 14:08:38 -0400 [thread overview]
Message-ID: <87eemxy6zd.fsf@gmail.com> (raw)
In-Reply-To: <87o9lr6qvu.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 18 Jan 2018 18:03:33 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mathieu Lirzin <mthl@gnu.org> skribis:
>
>> Mathieu Lirzin <mthl@gnu.org> writes:
>>
>>> ludo@gnu.org (Ludovic Courtès) writes:
>>>
>>>> Mathieu Lirzin <mthl@gnu.org> skribis:
>>>>
>>>>> My previous snippet didn't include the actual error
>>>>>
>>>>> TEST: tests/test-hmp... (pid=27743)
>>>>> /arm/hmp/integratorcp: OK
>>>>> /arm/hmp/nuri: qemu-system-arm: cannot set up guest memory
>>>>> 'exynos4210.dram0': Cannot allocate memory
>>>>> Broken pipe
>>>>> FAIL
>>>>> GTester: last random seed: R02S53adf2b44f1ff46cb48bd55ebce8854c
>>>>> (pid=27751)
>>>>> /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 allocate memory
>>>>> Broken pipe
>>>>> FAIL
>>>>>
>>>>> I have tried to build QEMU again with the same guix version and succeed.
>>>>> 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 ‘guix system build’. After the compilation 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’.
Closing this stale bug report against QEMU 2. We have fresher ones
against QEMU 5 :-).
Maxim
prev parent reply other threads:[~2020-09-19 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 18:53 bug#28111: qemu testsuite fails ng0
2017-08-16 19:35 ` ng0
2018-01-17 20:18 ` Mathieu Lirzin
2018-01-18 0:35 ` Mathieu Lirzin
2018-01-18 10:34 ` Ludovic Courtès
2018-01-18 12:58 ` Mathieu Lirzin
2018-01-18 15:52 ` Mathieu Lirzin
2018-01-18 17:03 ` Ludovic Courtès
2020-09-19 18:08 ` Maxim Cournoyer [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
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=87eemxy6zd.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=28111-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mthl@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).