| Message ID | 20200501082806.205696-1-stefanha@redhat.com |
|---|---|
| State | New |
| Headers | show |
Patchew URL: https://patchew.org/QEMU/20200501082806.205696-1-stefanha@redhat.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make docker-image-centos7 V=1 NETWORK=1
time make docker-test-quick@centos7 SHOW_ENV=1 J=14 NETWORK=1
=== TEST SCRIPT END ===
TEST iotest-qcow2: 074
socket_accept failed: Resource temporarily unavailable
**
ERROR:/tmp/qemu-test/src/tests/qtest/libqtest.c:301:qtest_init_without_qmp_handshake: assertion failed: (s->fd >= 0 && s->qmp_fd >= 0)
/tmp/qemu-test/src/tests/qtest/libqtest.c:166: kill_qemu() tried to terminate QEMU process but encountered exit status 1 (expected 0)
ERROR - Bail out! ERROR:/tmp/qemu-test/src/tests/qtest/libqtest.c:301:qtest_init_without_qmp_handshake: assertion failed: (s->fd >= 0 && s->qmp_fd >= 0)
make: *** [check-qtest-aarch64] Error 1
make: *** Waiting for unfinished jobs....
TEST iotest-qcow2: 079
TEST iotest-qcow2: 080
---
Not run: 259
Failures: 249
Failed 1 of 117 iotests
make: *** [check-tests/check-block.sh] Error 1
Traceback (most recent call last):
File "./tests/docker/docker.py", line 664, in <module>
sys.exit(main())
---
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=57718c949eb54215807b45721021e7ee', '-u', '1003', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=1', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew2/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-kc_n7mcq/src/docker-src.2020-05-01-04.40.40.25959:/var/tmp/qemu:z,ro', 'qemu:centos7', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2.
filter=--filter=label=com.qemu.instance.uuid=57718c949eb54215807b45721021e7ee
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-kc_n7mcq/src'
make: *** [docker-run-test-quick@centos7] Error 2
real 21m18.481s
user 0m10.757s
The full log is available at
http://patchew.org/logs/20200501082806.205696-1-stefanha@redhat.com/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
On Fri, 1 May 2020 at 09:28, Stefan Hajnoczi <stefanha@redhat.com> wrote: > > The following changes since commit 27c94566379069fb8930bb1433dcffbf7df3203d: > > Merge remote-tracking branch 'remotes/edgar/tags/edgar/xilinx-next-2020-04-30.for-upstream' into staging (2020-04-30 16:47:23 +0100) > > are available in the Git repository at: > > https://github.com/stefanha/qemu.git tags/block-pull-request > > for you to fetch changes up to cc1adc4488059ac16d4d2772a7aa7cd1323deeca: > > lockable: Replace locks with lock guard macros (2020-05-01 09:19:25 +0100) > > ---------------------------------------------------------------- > Pull request > > Fix the QEMU_LOCK_GUARD() macros, use them more widely, and allow the fuzzer > target to be selected from argv[0]. > > ---------------------------------------------------------------- Hi; this pullreq seems to include a stray change to the slirp submodule in the "fuzz: select fuzz target using executable name" commit. Could you fix that and resend, please? (You might like to include a molly-guard in your pullreq creation scripts; on my end I catch this sort of thing when applying with a test like if git diff master..staging | grep -q 'Subproject commit'; then # complain and exit unless I used an explicit command # line option to say I intended to include a submodule update fi though I haven't yet put the same test in the script I use to send pullreqs, for some reason. I guess my workflow now means I don't tend to accidentally commit submodule changes.) thanks -- PMM
On Fri, May 01, 2020 at 10:32:02AM +0100, Peter Maydell wrote: > On Fri, 1 May 2020 at 09:28, Stefan Hajnoczi <stefanha@redhat.com> wrote: > > > > The following changes since commit 27c94566379069fb8930bb1433dcffbf7df3203d: > > > > Merge remote-tracking branch 'remotes/edgar/tags/edgar/xilinx-next-2020-04-30.for-upstream' into staging (2020-04-30 16:47:23 +0100) > > > > are available in the Git repository at: > > > > https://github.com/stefanha/qemu.git tags/block-pull-request > > > > for you to fetch changes up to cc1adc4488059ac16d4d2772a7aa7cd1323deeca: > > > > lockable: Replace locks with lock guard macros (2020-05-01 09:19:25 +0100) > > > > ---------------------------------------------------------------- > > Pull request > > > > Fix the QEMU_LOCK_GUARD() macros, use them more widely, and allow the fuzzer > > target to be selected from argv[0]. > > > > ---------------------------------------------------------------- > > Hi; this pullreq seems to include a stray change to the slirp > submodule in the "fuzz: select fuzz target using executable name" > commit. Could you fix that and resend, please? > > (You might like to include a molly-guard in your pullreq > creation scripts; on my end I catch this sort of thing > when applying with a test like > if git diff master..staging | grep -q 'Subproject commit'; then > # complain and exit unless I used an explicit command > # line option to say I intended to include a submodule update > fi > > though I haven't yet put the same test in the script I use > to send pullreqs, for some reason. I guess my workflow now > means I don't tend to accidentally commit submodule changes.) Sorry for the spurious change. Will send a v2! Stefan