On Wed, Dec 19, 2012 at 11:04:38AM +0000, Daniel P. Berrange wrote:
> On Wed, Dec 19, 2012 at 09:59:45AM +0000, Daniel P. Berrange wrote:
> > On Wed, Dec 19, 2012 at 10:50:42AM +0100, Guido Günther wrote:
> > > Hi,
> > > it seems one of these commits
> > >
> > > 5411e7e176dcbb65591cb97ec128b5fd0f365805
> > > 473011334ccd93e8efbb67f2561f1d4e54d212ae
> > > 392c192240566d9e167d2b5a1022092d8f7e045c
> > >
> > > broke "make check" as seen on
> > >
> > >
http://honk.sigxcpu.org:8001/job/libvirt-check/417/console
> > >
> > > output attached. I can't look into this in more right now though.
> > > Cheers,
> > > -- Guido
> >
> > Thanks, I'll figure this out & provide patches. I rather screwed up
the
> > testing of the virArch patches due to a nunber of mistakes on my dev
> > machine :-(
>
> With the fixes I just pushed, I hope this should be working now.
> I tested with everything configure option except AppArmor enabled
> now.
All back to green. Thanks a lot! I wonder if it would make sense to
automatically forward "make and make check" failures to this or rather a
special list?
Assuming it is reliable (ie not generating too many false reports), then
there's no reason we can't have it sending straight to this list.
Regards,
Daniel
--
|: