[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [OSSTEST Nested PATCH v11 6/7] Compose the main recipe of nested test job



On Thu, 2015-06-11 at 07:41 +0000, Pang, LongtaoX wrote:
> 
> > -----Original Message-----
> > From: Ian Jackson [mailto:Ian.Jackson@xxxxxxxxxxxxx]
> > Sent: Wednesday, June 10, 2015 11:42 PM
> > To: Pang, LongtaoX
> > Cc: xen-devel@xxxxxxxxxxxxx; Ian.Campbell@xxxxxxxxxx; wei.liu2@xxxxxxxxxx; 
> > Hu,
> > Robert
> > Subject: Re: [OSSTEST Nested PATCH v11 6/7] Compose the main recipe of 
> > nested
> > test job
> > 
> > longtao.pang writes ("[OSSTEST Nested PATCH v11 6/7] Compose the main recipe
> > of nested test job"):
> > > The ident and guestname are same of 'nestedl1' for L1 guest VM.
> > 
> > This is going in the right direction.
> > 
> > I think arrangements need to be made to capture the logs for
> > nestedl1.
> > 
> I am sorry, what logs do you mean?

I think the ones gathered from a host by ts-logs-capture, which should
be made to run against an L1 hypervisor and added to the job recipe.

> > I think some extra +s in the l2 install and start operations might be
> > useful, because the testid probably doesn't need to mention nestedl1.
> > 
> I am sorry, do you mean that I should add '+' for l2 installation, 
> such as ' ts-debian-hvm-install + nestedl1 + nestedl2' ? 

You can use standalone --dry-run to see all the testid's generated by
your job and then adjust the +'s until they are as desired (in this case
Ian is suggesting to omit nestedl1 from the testid).

Ian.


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.