On Fri, Apr 08, 2011 at 09:58:22AM -0300, Lucas Meneghel Rodrigues wrote:
> On Thu, 2011-04-07 at 11:03 +0100, Stefan Hajnoczi wrote:
> > On Tue, Apr 5, 2011 at 6:37 PM, Lucas Meneghel Rodrigues
> > wrote:
> > >> Perhaps kvm-autotest is a good platform for the automated testing of
> > >> ARM TCG.
On Thu, 2011-04-07 at 11:03 +0100, Stefan Hajnoczi wrote:
> On Tue, Apr 5, 2011 at 6:37 PM, Lucas Meneghel Rodrigues
> wrote:
>
> Thanks for your detailed response!
>
> > On Tue, 2011-04-05 at 16:29 +0100, Stefan Hajnoczi wrote:
> >> * Public notifications of breakage, qemu.git/master failures
On Tue, Apr 5, 2011 at 6:37 PM, Lucas Meneghel Rodrigues
wrote:
Thanks for your detailed response!
> On Tue, 2011-04-05 at 16:29 +0100, Stefan Hajnoczi wrote:
>> * Public notifications of breakage, qemu.git/master failures to
>> qemu-devel mailing list.
>
> ^ The challenge is to get enough data
On Tue, 2011-04-05 at 16:29 +0100, Stefan Hajnoczi wrote:
> Features that I think are important for a qemu.git kvm-autotest:
> * Public results display (sounds like you're working on this)
^ Yes, we hope to get this setup soon.
> * Public notifications of breakage, qemu.git/master failures to
>
On Tue, Apr 5, 2011 at 4:07 PM, Chris Wright wrote:
> kvm-autotest
> - roadmap...refactor to centralize testing (handle the xen-autotest split off)
> - internally at RH, lmr and cleber maintain autotest server to test
> branches (testing qemu.git daily)
> - have good automation for installs and
KVM Forum
- save the date is out, cfp will follow later this week
- abstracts due in 6wks, 2wk review period, notifications by end of May
Improving process to scale project
- Trivial patch bot
- Sub-maintainership
Trivial patch monkeys^Wteam
- small/simple patches posted can fall through the crac
