On Tue, Nov 05, 2019 at 08:25:03PM +0000, Alex Bennée wrote: > > Eduardo Habkost <ehabk...@redhat.com> writes: > > > On Thu, Oct 31, 2019 at 08:12:01AM +0000, Peter Maydell wrote: > >> On Fri, 25 Oct 2019 at 21:34, Eduardo Habkost <ehabk...@redhat.com> wrote: > >> > > >> > The following changes since commit > >> > 03bf012e523ecdf047ac56b2057950247256064d: > >> > > >> > Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into > >> > staging (2019-10-25 14:59:53 +0100) > >> > > >> > are available in the Git repository at: > >> > > >> > git://github.com/ehabkost/qemu.git tags/python-next-pull-request > >> > > >> > for you to fetch changes up to d24e417866f85229de1b75bc5c0a1d942451a842: > >> > > >> > configure: Require Python >= 3.5 (2019-10-25 16:34:57 -0300) > >> > > >> > ---------------------------------------------------------------- > >> > Require Python >= 3.5 to build QEMU > >> > > >> > ---------------------------------------------------------------- > >> > >> I can't apply this until we've fixed the tests/vm netbsd setup to > >> not use Python 2. > > > > Fixing tests/vm/netbsd is being tricky. It looks like the > > configure patch will have to wait until after QEMU 4.2.0. :( > > I've posted fixes for the netbsd serial install but there are still > problems with the tests including what looks like a fairly serious > failure in the async code.
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. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
