From: Mathieu Lirzin <mthl@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28111@debbugs.gnu.org
Subject: bug#28111: qemu testsuite fails
Date: Thu, 18 Jan 2018 13:58:49 +0100 [thread overview]
Message-ID: <87tvvjtjau.fsf@gnu.org> (raw)
In-Reply-To: <87wp0fa20f.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 18 Jan 2018 11:34:56 +0100")
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.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
next prev parent reply other threads:[~2018-01-18 13:00 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 [this message]
2018-01-18 15:52 ` Mathieu Lirzin
2018-01-18 17:03 ` Ludovic Courtès
2020-09-19 18:08 ` Maxim Cournoyer
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=87tvvjtjau.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=28111@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 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.