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. :( > > Have you tried a test run with Travis/etc/etc to check that none of > those CI configs need updating to have python3 available ? I have tested this pull request on Shippable, and I will take a look at Travis. I'd appreciate help from the CI system maintainers (CCed) for the rest, as I don't have accounts in all our CI systems. Do we expect maintainers to test their pull requests in all CI systems listed at the QEMU wiki[1]? Do we have an official list of CI systems that you consider to be pull request blockers? [1] https://wiki.qemu.org/Testing#Continuous_Integration -- Eduardo
