qemu testsuite fails

  • Done
  • quality assurance status badge
Details
4 participants
  • Ludovic Courtès
  • Maxim Cournoyer
  • Mathieu Lirzin
  • ng0
Owner
unassigned
Submitted by
ng0
Severity
normal
N
(address . bug-guix@gnu.org)
20170816185317.3udxvtcclqkoqwkx@abyayala
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
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmUlJ0ACgkQ4i+bv+40
hYhmtg//Qt9wP2ogYmEUcICJRZ1fDwTr2zUPbI45GvjDuQq2k0xHY3E363/1xMyS
zFNazfGvZVqZ1TT2xrJSnSZ8JXcXObS9dNT6C0zT8hpZMEBPBixQBkwjjKl+6sJt
fs260VVh+4R6/AImVTnGBFCcteyytM99hwvqPAZOl7IL5Agxrq+aJZsm/hPs3bYF
/zjcFtn3WQKMOz+Ua5gu7uL+ppPgG/0AxnP52bhKsL4cZDNiZ+y7sw5WftSfGpku
4N5VcBlExAEBJtRvsPFeYMxhyJxGdTilsGTJ03AsItZqL0ft0sxYWkFyl1wn3/W1
brlGUB/oaTuNys0PcbpoSb6l7Cq6TN3Xjzy2HkRX15FwkmDckeX9NYCWVTNcCzzP
0Tuilj2bd6h0xctxaWVLN597NnVXpUhCyxukk45gbgYJRidhPcYCHl4jpoo8I6go
rGzfuZ5My4MChGIBe0nGWJsSd5cUtYMZbEYCPSuA5IoNjvMCdcgMaXDqZ7j4eC6c
NfxWx9ETOD5CEEmIWjtJQw7pQzO3yk6XOfme8UnbejVG/lczasCzmiecUAhZpkVe
74AM5JCnyc4sFMG+/O9oj2JPGWmg3GsKlcgYLpVEBM07bPJYQRa4y4WvQh46zuz3
7UtUfKEp02wMU3lXX72m+cyZPpM10rfNzaGuDfT7mxc1Bgvv37s=
=zPdN
-----END PGP SIGNATURE-----


N
(address . 28111@debbugs.gnu.org)
20170816193516.gb624goutduaj4rn@abyayala
ng0 transcribed 2.2K bytes:
Toggle quote (20 lines)
> 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
>

Ran it again, the second time I can't reproduce this.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmUnnQACgkQ4i+bv+40
hYghPQ//WOeHEAVOcLMt2ngJ7cHiCNoX5Wgdhgz6VXvQ2g8NBhhl2u/MtOg6ZEJ/
eBCTxy/T5wVdwcVRYVYoq2s+Tda6Y4+XrbTionv7HhjXoyXj01z+v6V4QHRK0+rH
1Fq9qJvN0wVuWyvkZgjM6HxG6lGQzwpYPlhLNAdrv79Yvyy/E09UnBfcULndNKDn
Zsd462JHOb7nqw/dqY9huH/CZ1yGDTMKUamKa7FoyhL/OknfKGAPy9+ITT1h4gEi
EZaMPFfe8LMO0L0wjIAN0zuSozWplwSWz6VQo7F5d1RspWA+tfXzHRv8fz+VmRMe
dDC53Pfrpt4j1nLRPNUjyZJobvV0YnyOnj8chUwn811ouc2tPjSMTIKlCBnbZolB
NIe3UC4GGaDfVGdbk/VPF41P9m4UJ2fu+5bQLQn5y36/sIO48B4yqmyGsifJ6Z09
VhIfvud02RhFV+S9UCDN2HHnrrEq+0/dyXT8RbhskPWp/vYe0BogWRNR0bqUIvHQ
1vegP3qwpZDX5xbjM3+lYfILzogA884Sqs92GhQDmn9LGBGybg1eTCCjqRIi8rl2
Q5ooLZkKG8ChZ6RZz6WdZWGZZx+F672+ieeSXInWdhrkD8K579dBp9Br2g71dvAI
raVj9AknE0vj1MTBCNpNNcq7x5rikkLcsJ5VfgGJklyNNhE3BUU=
=tegB
-----END PGP SIGNATURE-----


M
M
Mathieu Lirzin wrote on 17 Jan 2018 21:18
(address . 28111@debbugs.gnu.org)
87bmhsi6ig.fsf@gnu.org
Hello,

While running ‘guix package -u’ on my laptop, I have got the following
error during QEMU compilation ‘check’ phase:

Toggle snippet (61 lines)
...
GTester: last random seed: R02S1eb410daedbf83db3c3816109d49cf54
(pid=27765)
/arm/hmp/collie: OK
/arm/hmp/imx25-pdk: OK
/arm/hmp/none: OK
/arm/hmp/spitz: OK
/arm/hmp/realview-pbx-a9: OK
/arm/hmp/realview-eb: OK
/arm/hmp/versatilepb: OK
/arm/hmp/realview-pb-a8: OK
/arm/hmp/virt-2.9: OK
/arm/hmp/musicpal: OK
/arm/hmp/z2: OK
/arm/hmp/akita: OK
/arm/hmp/virt-2.7: OK
/arm/hmp/kzm: OK
/arm/hmp/virt-2.8: OK
/arm/hmp/realview-eb-mpcore: OK
/arm/hmp/sx1: OK
/arm/hmp/sx1-v1: OK
/arm/hmp/virt-2.6: OK
/arm/hmp/cubieboard: OK
/arm/hmp/highbank: OK
/arm/hmp/raspi2: OK
/arm/hmp/netduino2: OK
/arm/hmp/terrier: OK
/arm/hmp/n810: OK
/arm/hmp/mainstone: OK
/arm/hmp/palmetto-bmc: OK
/arm/hmp/sabrelite: OK
/arm/hmp/midway: OK
/arm/hmp/romulus-bmc: OK
/arm/hmp/cheetah: OK
/arm/hmp/tosa: OK
/arm/hmp/borzoi: OK
/arm/hmp/versatileab: OK
/arm/hmp/lm3s6965evb: OK
/arm/hmp/n800: OK
/arm/hmp/virt-2.10: OK
/arm/hmp/connex: OK
/arm/hmp/xilinx-zynq-a9: OK
/arm/hmp/mps2-an385: OK
/arm/hmp/vexpress-a9: OK
/arm/hmp/vexpress-a15: OK
/arm/hmp/canon-a1100: OK
/arm/hmp/lm3s811evb: OK
FAIL: tests/test-hmp
make: *** [/tmp/guix-build-qemu-2.10.2.drv-0/qemu-2.10.2/tests/Makefile.include:837: check-qtest-arm] Error 1
phase `check' failed after 197.4 seconds
builder for `/gnu/store/ab3qvykdhc11y12l575dhq2y8aibi040-qemu-2.10.2.drv' failed with exit code 1
guix package: error: build failed: build of `/gnu/store/ab3qvykdhc11y12l575dhq2y8aibi040-qemu-2.10.2.drv' failed

$ LC_ALL=C guix --version
guix (GNU Guix) d067e4badcaa705d8cb68d81c534ba69c3fa6e13
Copyright (C) 2018 the Guix authors
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Thanks.

--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
M
M
Mathieu Lirzin wrote on 18 Jan 2018 01:35
(address . 28111@debbugs.gnu.org)
873734hul6.fsf@gnu.org
Mathieu Lirzin <mthl@gnu.org> writes:

Toggle quote (9 lines)
> /arm/hmp/connex: OK
> /arm/hmp/xilinx-zynq-a9: OK
> /arm/hmp/mps2-an385: OK
> /arm/hmp/vexpress-a9: OK
> /arm/hmp/vexpress-a15: OK
> /arm/hmp/canon-a1100: OK
> /arm/hmp/lm3s811evb: OK
> FAIL: tests/test-hmp

My previous snippet didn't include the actual error

Toggle snippet (15 lines)
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.

--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
L
L
Ludovic Courtès wrote on 18 Jan 2018 11:34
(name . Mathieu Lirzin)(address . mthl@gnu.org)(address . 28111@debbugs.gnu.org)
87wp0fa20f.fsf@gnu.org
Mathieu Lirzin <mthl@gnu.org> skribis:

Toggle quote (19 lines)
> 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?

(Also, too bad there were no substitutes at the time you installed!)

Ludo’.
M
M
Mathieu Lirzin wrote on 18 Jan 2018 13:58
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 28111@debbugs.gnu.org)
87tvvjtjau.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) writes:

Toggle quote (23 lines)
> 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
M
M
Mathieu Lirzin wrote on 18 Jan 2018 16:52
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 28111@debbugs.gnu.org)
87607z6u5m.fsf@gnu.org
Mathieu Lirzin <mthl@gnu.org> writes:

Toggle quote (29 lines)
> 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.

--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
L
L
Ludovic Courtès wrote on 18 Jan 2018 18:03
(name . Mathieu Lirzin)(address . mthl@gnu.org)(address . 28111@debbugs.gnu.org)
87o9lr6qvu.fsf@gnu.org
Mathieu Lirzin <mthl@gnu.org> skribis:

Toggle quote (36 lines)
> 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’.
M
M
Maxim Cournoyer wrote on 19 Sep 2020 20:08
(name . Ludovic Courtès)(address . ludo@gnu.org)
87eemxy6zd.fsf@gmail.com
ludo@gnu.org (Ludovic Courtès) writes:

Toggle quote (47 lines)
> 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
Closed
M
M
Maxim Cournoyer wrote on 19 Sep 2020 20:08
control message for bug #28111
(address . control@debbugs.gnu.org)
87d02hy6ys.fsf@gmail.com
tags 28111 fixed
close 28111
quit
?