From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
vsementsov@virtuozzo.com
Cc: kwolf@redhat.com, den@openvz.org, stefanha@redhat.com,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH v3 for-5.1 0/2] Fix crash due to NBD export leak
Date: Tue, 14 Jul 2020 19:26:12 +0200 [thread overview]
Message-ID: <8474b170-afbf-3e2f-022f-dbf018f7da07@redhat.com> (raw)
In-Reply-To: <159474538053.11884.16567641221376136360@07a7f0d89f7d>
Cc'ing Marc-André
On 7/14/20 6:49 PM, no-reply@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20200714162234.13113-1-vsementsov@virtuozzo.com/
...
>
> TEST iotest-qcow2: 022
> TEST check-unit: tests/test-char
> **
> ERROR:/tmp/qemu-test/src/tests/test-char.c:1204:char_serial_test: 'chr' should not be NULL
> ERROR test-char - Bail out! ERROR:/tmp/qemu-test/src/tests/test-char.c:1204:char_serial_test: 'chr' should not be NULL
Seems related to latest chardev-pull-request.
> make: *** [check-unit] Error 1
> make: *** Waiting for unfinished jobs....
> TEST iotest-qcow2: 024
> TEST iotest-qcow2: 025
> ---
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=9dc2c7a6e3eb458c88fdd6be6a03c6eb', '-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-fzvixkio/src/docker-src.2020-07-14-12.32.53.19697:/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=9dc2c7a6e3eb458c88fdd6be6a03c6eb
> make[1]: *** [docker-run] Error 1
> make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-fzvixkio/src'
> make: *** [docker-run-test-quick@centos7] Error 2
>
> real 16m48.396s
> user 0m8.741s
>
>
> The full log is available at
> http://patchew.org/logs/20200714162234.13113-1-vsementsov@virtuozzo.com/testing.docker-quick@centos7/?type=message.
next prev parent reply other threads:[~2020-07-14 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 16:22 [PATCH v3 for-5.1 0/2] Fix crash due to NBD export leak Vladimir Sementsov-Ogievskiy
2020-07-14 16:22 ` [PATCH v3 1/2] nbd: make nbd_export_close_all() synchronous Vladimir Sementsov-Ogievskiy
2020-07-14 16:22 ` [PATCH v3 2/2] iotests: test shutdown when bitmap is exported through NBD Vladimir Sementsov-Ogievskiy
2020-07-14 16:49 ` [PATCH v3 for-5.1 0/2] Fix crash due to NBD export leak no-reply
2020-07-14 16:59 ` Vladimir Sementsov-Ogievskiy
2020-07-14 17:26 ` Philippe Mathieu-Daudé [this message]
2020-07-17 12:01 ` Kevin Wolf
2020-07-17 15:00 ` Vladimir Sementsov-Ogievskiy
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=8474b170-afbf-3e2f-022f-dbf018f7da07@redhat.com \
--to=philmd@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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).