Report forwarded
to bug-guix@gnu.org: bug#28111; Package guix.
(Wed, 16 Aug 2017 18:55:02 GMT) (full text, mbox, link).
Acknowledgement sent
to ng0 <ng0@infotropique.org>:
New bug report received and forwarded. Copy sent to bug-guix@gnu.org.
(Wed, 16 Aug 2017 18:55:02 GMT) (full text, mbox, link).
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-keyshttps://www.infotropique.orghttps://krosos.org
ng0 transcribed 2.2K bytes:
> 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
GnuPG: https://n0is.noblogs.org/my-keyshttps://www.infotropique.orghttps://krosos.org
Hello,
While running ‘guix package -u’ on my laptop, I have got the following
error during QEMU compilation ‘check’ phase:
--8<---------------cut here---------------start------------->8---
...
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.
--8<---------------cut here---------------end--------------->8---
Thanks.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
Information forwarded
to bug-guix@gnu.org: bug#28111; Package guix.
(Thu, 18 Jan 2018 00:36:02 GMT) (full text, mbox, link).
Mathieu Lirzin <mthl@gnu.org> writes:
> /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
--8<---------------cut here---------------start------------->8---
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
--8<---------------cut here---------------end--------------->8---
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
Information forwarded
to bug-guix@gnu.org: bug#28111; Package guix.
(Thu, 18 Jan 2018 10:35:02 GMT) (full text, mbox, link).
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?
(Also, too bad there were no substitutes at the time you installed!)
Ludo’.
Information forwarded
to bug-guix@gnu.org: bug#28111; Package guix.
(Thu, 18 Jan 2018 13:00:02 GMT) (full text, mbox, link).
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
Information forwarded
to bug-guix@gnu.org: bug#28111; Package guix.
(Thu, 18 Jan 2018 15:54:02 GMT) (full text, mbox, link).
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.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
Information forwarded
to bug-guix@gnu.org: bug#28111; Package guix.
(Thu, 18 Jan 2018 17:04:01 GMT) (full text, mbox, link).
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’.
Reply sent
to Maxim Cournoyer <maxim.cournoyer@gmail.com>:
You have taken responsibility.
(Sat, 19 Sep 2020 18:08:01 GMT) (full text, mbox, link).
Notification sent
to ng0 <ng0@infotropique.org>:
bug acknowledged by developer.
(Sat, 19 Sep 2020 18:08:02 GMT) (full text, mbox, link).
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
Added tag(s) fixed.
Request was from Maxim Cournoyer <maxim.cournoyer@gmail.com>
to control@debbugs.gnu.org.
(Sat, 19 Sep 2020 18:09:01 GMT) (full text, mbox, link).
bug archived.
Request was from Debbugs Internal Request <help-debbugs@gnu.org>
to internal_control@debbugs.gnu.org.
(Sun, 18 Oct 2020 11:24:05 GMT) (full text, mbox, link).
Debbugs is free software and licensed under the terms of the
GNU Public License version 2. The current version can be
obtained from https://bugs.debian.org/debbugs-source/.