From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Stefan Weil" <sw@weilnetz.de>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/4] docs: convert README, CODING_STYLE and HACKING to RST syntax
Date: Mon, 09 Sep 2019 16:14:04 +0100 [thread overview]
Message-ID: <87pnk91ozn.fsf@linaro.org> (raw)
In-Reply-To: <4babad28-f2d2-40d1-fc5b-6eaac479676a@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 09/09/19 15:20, Philippe Mathieu-Daudé wrote:
>>> Doh. If we care about NSIS, we really need to have it being tested by
>>> some part of our CI system, and by pre-merge build tests.
>>
>> I believe Stefan Weil does, since he regularly sends fixes or opens LP
>> bugs during freeze time.
>>
>> We do build nsis/win32 with CI, but for some reason patchew was down.
>>
>> I'm not sure we should duplicate the build on another CI, we should
>> rather setup something to watch patchew and warn us when it goes down.
>
> I'm not sure what happened since I (obviously) was not monitoring
> patchew during my vacation. However, the recent Python 3 port of
> docker.py bumped the requirement to Python 3.6 to run "make docker"
> tests, and this broke patchew which had an older version. I have now
> updated the tester.
FWIW testing/next fixes the over eager python3 upgrade (I hadn't
realised how recent encoding was as a check_output keyword). Expect it
in a PR in the next few days.
>
> Paolo
--
Alex Bennée
next prev parent reply other threads:[~2019-09-09 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 16:50 [Qemu-devel] [PATCH v3 0/4] docs: add docs about use of automatic cleanup functions Daniel P. Berrangé
2019-08-29 16:50 ` [Qemu-devel] [PATCH v3 1/4] docs: convert README, CODING_STYLE and HACKING to RST syntax Daniel P. Berrangé
2019-09-09 12:57 ` Philippe Mathieu-Daudé
2019-09-09 13:15 ` Daniel P. Berrangé
2019-09-09 13:20 ` Philippe Mathieu-Daudé
2019-09-09 14:25 ` Paolo Bonzini
2019-09-09 15:14 ` Alex Bennée [this message]
2019-08-29 16:50 ` [Qemu-devel] [PATCH v3 2/4] docs: merge HACKING.rst contents into CODING_STYLE.rst Daniel P. Berrangé
2019-09-05 14:43 ` Eric Blake
2019-08-29 16:50 ` [Qemu-devel] [PATCH v3 3/4] docs: document use of automatic cleanup functions in glib Daniel P. Berrangé
2019-09-05 14:46 ` Eric Blake
2019-08-29 16:50 ` [Qemu-devel] [PATCH v3 4/4] docs: split the CODING_STYLE doc into distinct groups Daniel P. Berrangé
2019-09-05 13:31 ` Peter Maydell
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=87pnk91ozn.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=sw@weilnetz.de \
/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).