From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org, vsementsov@virtuozzo.com
Cc: kwolf@redhat.com, fam@euphon.net, ehabkost@redhat.com,
qemu-block@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
crosa@redhat.com, den@openvz.org
Subject: Re: [PATCH v5 0/7] coroutines: generate wrapper code
Date: Wed, 27 May 2020 16:57:14 -0500 [thread overview]
Message-ID: <4a4d5dc4-4cab-ad59-a4d3-6f84de1aa1e3@redhat.com> (raw)
In-Reply-To: <159061599705.16318.11961887809600256765@45ef0f9c86ae>
On 5/27/20 4:46 PM, no-reply@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20200527203733.16129-1-vsementsov@virtuozzo.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 ===
>
> TypeError: __init__() got an unexpected keyword argument 'capture_output'
> CC /tmp/qemu-test/build/slirp/src/bootp.o
> GEN ui/input-keymap-usb-to-qcode.c
> make: *** [block/block-gen.c] Error 1
> make: *** Deleting file `block/block-gen.c'
> make: *** Waiting for unfinished jobs....
> GEN ui/input-keymap-win32-to-qcode.c
The more interesting part of the failure:
File "/tmp/qemu-test/src/scripts/coroutine-wrapper.py", line 173, in
<module>
print(gen_wrappers_file(sys.stdin.read()))
File "/tmp/qemu-test/src/scripts/coroutine-wrapper.py", line 169, in
gen_wrappers_file
return prettify(res) # prettify to wrap long lines
File "/tmp/qemu-test/src/scripts/coroutine-wrapper.py", line 40, in
prettify
encoding='utf-8', input=code, capture_output=True)
File "/usr/lib64/python3.6/subprocess.py", line 423, in run
with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'
which indeed looks like a bug in the patch.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-05-27 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 20:37 [PATCH v5 0/7] coroutines: generate wrapper code Vladimir Sementsov-Ogievskiy
2020-05-27 20:37 ` [PATCH v5 1/7] block: return error-code from bdrv_invalidate_cache Vladimir Sementsov-Ogievskiy
2020-05-27 22:03 ` Eric Blake
2020-05-27 20:37 ` [PATCH v5 2/7] block/io: refactor coroutine wrappers Vladimir Sementsov-Ogievskiy
2020-05-27 20:37 ` [PATCH v5 3/7] block: declare some coroutine functions in block/coroutines.h Vladimir Sementsov-Ogievskiy
2020-05-27 20:37 ` [PATCH v5 4/7] scripts: add coroutine-wrapper.py Vladimir Sementsov-Ogievskiy
2020-05-27 20:37 ` [PATCH v5 5/7] block: generate coroutine-wrapper code Vladimir Sementsov-Ogievskiy
2020-05-27 20:37 ` [PATCH v5 6/7] block: drop bdrv_prwv Vladimir Sementsov-Ogievskiy
2020-05-27 20:37 ` [PATCH v5 7/7] block/io: refactor save/load vmstate Vladimir Sementsov-Ogievskiy
2020-05-27 21:46 ` [PATCH v5 0/7] coroutines: generate wrapper code no-reply
2020-05-27 21:57 ` Eric Blake [this message]
2020-05-28 6:24 ` Vladimir Sementsov-Ogievskiy
2020-05-27 22:25 ` 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=4a4d5dc4-4cab-ad59-a4d3-6f84de1aa1e3@redhat.com \
--to=eblake@redhat.com \
--cc=crosa@redhat.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@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).