On (Tue) 05 Mar 2013 [12:54:06], Lucas Meneghel Rodrigues wrote:
> On 03/05/2013 07:11 AM, Amit Shah wrote:
> >On (Mon) 04 Mar 2013 [16:53:55], Stefan Hajnoczi wrote:
> >>How are things looking with device emulation, migration, monitor, char, etc?
> >
> >I have a few tests coded up for virtio-seri
Stefan Hajnoczi writes:
[...]
> The way that buildbot does this is and I think the same is possible for
> kvm autotest:
> 1. Send failure notifications to qemu-devel.
> 2. Provide a website to check the status
> http://buildbot.b1-systems.de/qemu/.
+1
[...]
On Tue, Mar 05, 2013 at 01:21:18PM -0300, Lucas Meneghel Rodrigues wrote:
> On 03/05/2013 01:14 PM, Gerd Hoffmann wrote:
> > Hi,
> >
> >>>I don't think we have *any* regular autotest coverage for master, have
> >>>we?
> >>
> >>^ Yes, there is coverage. There's a daily job called sanity that takes
On 03/05/2013 01:23 PM, Gerd Hoffmann wrote:
Hi,
On virt-tests there are at least 48 tests that are easy to run and
involve migration. A subset of them is executed regularly in the daily
jobs:
Sure, there are a bunch of tests already, which is good.
But there are also important areas which
Hi,
> On virt-tests there are at least 48 tests that are easy to run and
> involve migration. A subset of them is executed regularly in the daily
> jobs:
Sure, there are a bunch of tests already, which is good.
But there are also important areas which are not covered at all yet.
For example th
On 03/05/2013 01:14 PM, Gerd Hoffmann wrote:
Hi,
I don't think we have *any* regular autotest coverage for master, have
we?
^ Yes, there is coverage. There's a daily job called sanity that takes
about 2.5 hours, that builds the latest kvm.git and installs it in the
host, then reboots the b
Hi,
>> I don't think we have *any* regular autotest coverage for master, have
>> we?
>
> ^ Yes, there is coverage. There's a daily job called sanity that takes
> about 2.5 hours, that builds the latest kvm.git and installs it in the
> host, then reboots the box, builds the latest qemu master an
On 03/04/2013 01:22 PM, Gerd Hoffmann wrote:
Hi,
How are things looking with device emulation, migration, monitor, char, etc?
At the moment autotest/virt-test is pretty much the only workable thing
for non-trivial devices because libqtest lacks infrastructure for pci
and anything building
On 03/05/2013 08:17 AM, Gerd Hoffmann wrote:
On 03/05/13 11:46, Stefan Hajnoczi wrote:
On Mon, Mar 04, 2013 at 05:22:34PM +0100, Gerd Hoffmann wrote:
Hi,
How are things looking with device emulation, migration, monitor, char, etc?
At the moment autotest/virt-test is pretty much the only
On 03/05/2013 07:11 AM, Amit Shah wrote:
On (Mon) 04 Mar 2013 [16:53:55], Stefan Hajnoczi wrote:
People are working on testing for various parts of QEMU. I started
this thread to gather an update on the state of testing and see where
we still need help.
I'm not sure yet if we should propose Go
On 03/05/13 11:46, Stefan Hajnoczi wrote:
> On Mon, Mar 04, 2013 at 05:22:34PM +0100, Gerd Hoffmann wrote:
>> Hi,
>>
>>> How are things looking with device emulation, migration, monitor, char, etc?
>>
>> At the moment autotest/virt-test is pretty much the only workable thing
>> for non-trivial de
On Mon, Mar 04, 2013 at 05:22:34PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > How are things looking with device emulation, migration, monitor, char, etc?
>
> At the moment autotest/virt-test is pretty much the only workable thing
> for non-trivial devices because libqtest lacks infrastructure for
On Mon, Mar 04, 2013 at 01:20:03PM -0600, Anthony Liguori wrote:
> Stefan Hajnoczi writes:
>
> > People are working on testing for various parts of QEMU. I started
> > this thread to gather an update on the state of testing and see where
> > we still need help.
> >
> > I'm not sure yet if we sho
On (Mon) 04 Mar 2013 [16:53:55], Stefan Hajnoczi wrote:
> People are working on testing for various parts of QEMU. I started
> this thread to gather an update on the state of testing and see where
> we still need help.
>
> I'm not sure yet if we should propose Google Summer of Code projects
> to
Am 04.03.2013 um 17:22 hat Gerd Hoffmann geschrieben:
> Hi,
>
> > How are things looking with device emulation, migration, monitor, char, etc?
>
> At the moment autotest/virt-test is pretty much the only workable thing
> for non-trivial devices because libqtest lacks infrastructure for pci
> an
Stefan Hajnoczi writes:
> People are working on testing for various parts of QEMU. I started
> this thread to gather an update on the state of testing and see where
> we still need help.
>
> I'm not sure yet if we should propose Google Summer of Code projects
> to help with the testing infrastru
On Mon, Mar 04, 2013 at 05:22:34PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > How are things looking with device emulation, migration, monitor, char, etc?
>
> At the moment autotest/virt-test is pretty much the only workable thing
> for non-trivial devices because libqtest lacks infrastructure for
Hi,
> How are things looking with device emulation, migration, monitor, char, etc?
At the moment autotest/virt-test is pretty much the only workable thing
for non-trivial devices because libqtest lacks infrastructure for pci
and anything building on top of pci.
usb has no in-tree tests, but ha
People are working on testing for various parts of QEMU. I started
this thread to gather an update on the state of testing and see where
we still need help.
I'm not sure yet if we should propose Google Summer of Code projects
to help with the testing infrastructure. Perhaps working on libqtest
s
19 matches
Mail list logo
