On 12/29/2011 07:02 PM, Anthony Liguori wrote: > > Those are rare occurrences and have always been a bit awkward. OTOH, > we're talking about the critical path of essentially every single > feature that gets merged into QEMU. >
Won't that be qtest? Major features are rare. Small changes are common. >> Let's consider postcopy live migration being proposed. In addition to >> various unit tests, it also wants an integration test. So now we need >> to write a qemu-test postcopy live migration test, and also autotest >> test that tests non-Linux guests, migration under load, with memory >> hotplug, etc. > > But the integration test is also going to depend on libvirt support > for the feature. So how does this all get orchestrated? kvm-autotest > merges the test case first, then QEMU merges the support, then > libvirt? What about VDSM and ovirt-engine? Once kvm-autotest starts > supporting VDSM that's yet another component to deal with. > > Realistically, kvm-autotest is going to have to wait for the bits to > get merged in all of the necessary pieces and then build a test for it > on their own schedule. It just has to be posted and reviewed, it doesn't all have to be merged at the same time (and the qemu merge has to precede the autotest merge) -- error compiling committee.c: too many arguments to function
