On Tue, 5 Nov 2019 at 19:57, Eduardo Habkost <ehabk...@redhat.com> wrote: > Fixing tests/vm/netbsd is being tricky. It looks like the > configure patch will have to wait until after QEMU 4.2.0. :(
I think that makes sense at this point in the release cycle, yes. > > 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? No, I don't in general expect people to test on all these CI systems. I ask in this specific case because trying to move to python-3-only seems like a change that's quite likely to break the CI setups unless we've already checked that all their configs will be pulling in a python 3 already. thanks -- PMM
