From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
"Ed Maste" <emaste@freebsd.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: [PULL 0/1] Require Python >= 3.5 to build QEMU
Date: Wed, 06 Nov 2019 11:48:31 +0000 [thread overview]
Message-ID: <87v9rxi5tc.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA9LqhboQH5_NAJF5XbE+PbX16dYuRd60Tz_R_Y215QhMw@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Wed, 6 Nov 2019 at 10:36, Daniel P. Berrangé <berrange@redhat.com> wrote:
>> At what point do we declare that NetBSD CI is broken and is no longer
>> considered a supported platform from POV of blocking the merging of
>> PULL requests ? It has been preventing the dropping of python2 for
>> quite a while now. It isn't the end of the world in this particular
>> case, as dropping py2 is mostly just a cleanup, but I feel like we
>> might benefit from setting expectations for ongoing platform maintenance,
>> otherwise these kind of issues could drag on indefinitely.
>
> It works fine for me, and it means we have coverage of a host
> OS we otherwise would not. To me that is definitely more important
> than being able to drop Python 2 support. Also, AIUI the problem
> that's blocking updating the NetBSD image isn't related to
> NetBSD at all but is a bug in some combination of QEMU itself
> and our test framework
These have been addressed in:
Subject: [PATCH v1 0/6] testing/next (netbsd stuff)
Date: Mon, 4 Nov 2019 17:36:48 +0000
Message-Id: <20191104173654.30125-1-alex.bennee@linaro.org>
but I have a non-trivial failure rate running tests (~20% of runs fail)
> -- both of those are things we need to
> fix anyway.
>
> thanks
> -- PMM
--
Alex Bennée
prev parent reply other threads:[~2019-11-06 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 20:34 [PULL 0/1] Require Python >= 3.5 to build QEMU Eduardo Habkost
2019-10-25 20:34 ` [PULL 1/1] configure: Require Python >= 3.5 Eduardo Habkost
2019-10-31 8:12 ` [PULL 0/1] Require Python >= 3.5 to build QEMU Peter Maydell
2019-11-05 19:57 ` Eduardo Habkost
2019-11-05 20:10 ` Peter Maydell
2019-11-05 20:25 ` Alex Bennée
2019-11-05 20:36 ` Eduardo Habkost
2019-11-06 10:36 ` Daniel P. Berrangé
2019-11-06 11:17 ` Peter Maydell
2019-11-06 11:48 ` Alex Bennée [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=87v9rxi5tc.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=emaste@freebsd.org \
--cc=fam@euphon.net \
--cc=lwhsu@freebsd.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).