From: no-reply@patchew.org
To: thuth@redhat.com
Cc: kwolf@redhat.com, jsnow@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH v2 0/6] Enable more iotests during "make check-block"
Date: Mon, 21 Oct 2019 06:09:57 -0700 (PDT) [thread overview]
Message-ID: <157166339664.24734.15529210930104297381@37313f22b938> (raw)
In-Reply-To: <20191021105350.1710-1-thuth@redhat.com>
Patchew URL: https://patchew.org/QEMU/20191021105350.1710-1-thuth@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: 267
Failures: 183
Failed 1 of 116 iotests
make: *** [check-tests/check-block.sh] Error 1
Traceback (most recent call last):
File "./tests/docker/docker.py", line 662, in <module>
sys.exit(main())
---
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=f64a3cf2b9e04de3b3eaf1eda31d5b32', '-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-lh2_8bm3/src/docker-src.2019-10-21-08.54.52.18501:/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=f64a3cf2b9e04de3b3eaf1eda31d5b32
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-lh2_8bm3/src'
make: *** [docker-run-test-quick@centos7] Error 2
real 15m4.081s
user 0m8.752s
The full log is available at
http://patchew.org/logs/20191021105350.1710-1-thuth@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
next prev parent reply other threads:[~2019-10-21 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 10:53 [PATCH v2 0/6] Enable more iotests during "make check-block" Thomas Huth
2019-10-21 10:53 ` [PATCH v2 1/6] iotests: remove 'linux' from default supported platforms Thomas Huth
2019-10-21 10:53 ` [PATCH v2 2/6] iotests: Test 041 only works on certain systems Thomas Huth
2019-10-21 10:53 ` [PATCH v2 3/6] iotests: Test 183 does not work on macOS and OpenBSD Thomas Huth
2019-10-21 10:53 ` [PATCH v2 4/6] iotests: Skip "make check-block" if QEMU does not support virtio-blk Thomas Huth
2019-10-21 10:53 ` [PATCH v2 5/6] iotests: Enable more tests in the 'auto' group to improve test coverage Thomas Huth
2019-10-21 10:53 ` [PATCH v2 6/6] iotests: Remove 130 from the "auto" group Thomas Huth
2019-10-21 13:09 ` no-reply [this message]
2019-10-21 13:31 ` [PATCH v2 0/6] Enable more iotests during "make check-block" Thomas Huth
2019-10-21 17:03 ` no-reply
2019-10-21 17:03 ` no-reply
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=157166339664.24734.15529210930104297381@37313f22b938 \
--to=no-reply@patchew.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).