From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org, no-reply@patchew.org, tamiko@43-1.org
Cc: famz@redhat.com, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix compilation with python-3 if en_US.UTF-8 is unavailable
Date: Mon, 18 Jun 2018 17:15:53 -0500 [thread overview]
Message-ID: <d78e8f55-5527-1d8f-c38b-bcbcbb5ef381@redhat.com> (raw)
In-Reply-To: <152899585150.702.2589994392500110079@d39dc562802a>
On 06/14/2018 12:04 PM, no-reply@patchew.org wrote:
> Hi,
>
> This series failed build test on s390x host. Please find the details below.
>
> GEN qemu-options.def
> GEN qapi-gen
> GEN trace/generated-tcg-tracers.h
> /var/tmp/patchew-tester-tmp-j902xtzn/src/qapi/qapi-schema.json:56: Pragma returns-whitelist must be a list of strings
Your idea makes sense (force the encoding in our scripts that care about
encoding, rather than via the environment), but you'll need to resolve
this build failure first. Looking forward to v2.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-06-18 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 15:43 [Qemu-devel] [PATCH 0/2] Fix compilation with python-3 if en_US.UTF-8 is unavailable Matthias Maier
2018-06-14 15:43 ` [Qemu-devel] [PATCH 1/2] Partially revert commit d4e5ec877ca Matthias Maier
2018-06-15 20:34 ` Eduardo Habkost
2018-06-15 21:12 ` Matthias Maier
2018-06-14 15:43 ` [Qemu-devel] [PATCH 2/2] qapi: open files in binary mode and use explicit decoding/encoding in common.py Matthias Maier
2018-06-14 17:04 ` [Qemu-devel] [PATCH 0/2] Fix compilation with python-3 if en_US.UTF-8 is unavailable no-reply
2018-06-18 22:15 ` Eric Blake [this message]
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=d78e8f55-5527-1d8f-c38b-bcbcbb5ef381@redhat.com \
--to=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=famz@redhat.com \
--cc=no-reply@patchew.org \
--cc=qemu-devel@nongnu.org \
--cc=tamiko@43-1.org \
/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).