Re: [Xen-devel] libvirt / libxl testing emails

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Fri, 2014-06-06 at 17:32 +0800, Daniel Veillard wrote:
> On Fri, Jun 06, 2014 at 09:25:46AM +0100, Ian Campbell wrote:
> > On Wed, 2014-06-04 at 00:00 +0800, Daniel Veillard wrote:
> > > On Tue, Jun 03, 2014 at 03:16:49PM +0100, George Dunlap wrote:
> > > > Ian / Ian,
> > > > 
> > > > Daniel V. was lurking on a recent CentOS Virt SIG IRC meetings, and 
> > > > asked
> > > > about testing the libvirt git repo against libxl.  I mentioned that we
> > > > already had some basic tests to do that, and he asked whether it would 
> > > > make
> > > > sense to have the push gate e-mail the libvirt list.
> > > > 
> > > > I have no idea how the libvirt people feel about that, so I'll let DV 
> > > > make
> > > > his case, and also let he Ians give their opinions.
> > > 
> > >   Actually Dan Berrange should be included. I think the nicest would
> > > be a private ping and the information available online,
> > 
> > Why private and not to the libvir list?
> 
>   Well the point is that the libvir-list is already high traffic
> and avoiding automated mails to it would help.

Oh, I thought you were referring to my manual CC to libvirt that I have
been doing when an issue looked to be upstream related (exactly once so
far).

Yes, I certainly wouldn't recommend sending our automated test reports
to the list.

I'm happy to add an automated CC to whatever mailbox you guys want.

>  Also the compile
> box doesn't send mail directly to the list in case of breakage either,
> so that would be coherent.
> 
> > The information is available online via the test report (which don't
> > stay around forever, but for weeks at least).
> > 
> > I'm happy to do whatever you guys would prefer, just let me know.
> 
>   Do you have a pointer to where the test reports sit, that would be
> helpful as a first step :-)

There is a link in each test report e.g.
http://lists.xen.org/archives/html/xen-devel/2014-06/msg00776.html
links to
http://www.chiark.greenend.org.uk/~xensrcts/logs/26970/ note that the
logs are expired after a couple of weeks (this one is still live
though).

http://xenbits.xensource.com/gitweb/?p=osstest.git;a=blob;f=README;h=9a85549cb600fa5be91bcbae6605f78616db63da;hb=HEAD
 contains some terminology etc which might help you make sense of it.

Currently these are only build tests, because we've not taught our test
system about virsh yet, hence the "guest-start" step is marked as "never
passed".

By contrast
http://lists.xen.org/archives/html/xen-devel/2014-06/msg00557.html 
http://www.chiark.greenend.org.uk/~xensrcts/logs/26947/ is a failed test
(caused by a network glitch on our end)

http://lists.xen.org/archives/html/xen-devel/2014-05/msg00528.html has
some useful background one which test flights (flight == the FOO in the
"[FOO test]" but of the email subject) include libvirt tests and what
they are testing against what (summary: libvirt flight is new libvirt
against already tested xen and xen-* flights are new xen from that
branch against already an tested libvirt).

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel