bug#28111: closed (qemu testsuite fails)

[GNU bug Tracking System]

Your message dated Sat, 19 Sep 2020 14:08:38 -0400
with message-id <87eemxy6zd.fsf@gmail.com>
and subject line Re: bug#28111: qemu testsuite fails
has caused the debbugs.gnu.org bug report #28111,
regarding qemu testsuite fails
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
28111: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=28111
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: qemu testsuite fails Date: Wed, 16 Aug 2017 18:53:17 +0000

Maybe this occurs just occasionally, nevertheless worth
reporting. I have no time to look into fixing it right now.

TEST: tests/vhost-user-test... (pid=27813)
/i386/vhost-user/read-guest-mem:                                     OK
/i386/vhost-user/migrate:                                            OK
/i386/vhost-user/multiqueue:                                         OK
/i386/vhost-user/reconnect:                                          OK
/i386/vhost-user/connect-fail:                                       **
ERROR:tests/vhost-user-test.c:809:test_connect_fail: child process 
(/i386/vhost-user/connect-fail/subprocess [27843]) failed unexpectedly
qemu-system-i386: Failed to set msg fds.
qemu-system-i386: vhost VQ 0 ring restore failed: -1: Input/output error (5)
qemu-system-i386: Failed to set msg fds.
qemu-system-i386: vhost VQ 1 ring restore failed: -1: Input/output error (5)
FAIL
GTester: last random seed: R02S8558f45fe09086531252e03ae246aedb
(pid=27854)
/i386/vhost-user/flags-mismatch:                                     OK


-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

signature.asc
Description: PGP signature

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#28111: qemu testsuite fails
>
>
>
>
> Date: 
>
> Sat, 19 Sep 2020 14:08:38 -0400
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
>
>
>
>
> 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
>
>
> --- End Message ---