From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v8 2/2] OSSTest: push successful raisin builds Date: Tue, 4 Aug 2015 14:11:01 +0100 Message-ID: <1438693861.31129.109.camel@citrix.com> References: <1437670366-29034-2-git-send-email-stefano.stabellini@eu.citrix.com> <1438692978.31129.104.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1438692978.31129.104.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini , xen-devel@lists.xen.org Cc: ian.jackson@eu.citrix.com, wei.liu2@citrix.com List-Id: xen-devel@lists.xenproject.org On Tue, 2015-08-04 at 13:56 +0100, Ian Campbell wrote: > On Thu, 2015-07-23 at 17:52 +0100, Stefano Stabellini wrote: > > diff --git a/ap-fetch-version b/ap-fetch-version > > index 33aaf00..2788d9f 100755 > > --- a/ap-fetch-version > > +++ b/ap-fetch-version > > @@ -80,6 +80,9 @@ libvirt) > > rumpuserxen) > > repo_tree_rev_fetch_git rumpuserxen \ > > $TREE_RUMPUSERXEN master $LOCALREV_RUMPUSERXEN > > Missing ";;" here. If you are looking to test the ap-* stuff in a more realistic (i.e. closer to how production would call it) environment then you can do: For a flight named "raisin" testing the raisin branch: $ ./standalone make-flight -f raisin raisin For a flight named "standalone" (the default) testing xen-unstable: $ ./standalone make-flight xen-unstable You can then examine the contents of those two with mg-show-flight-runvars. You may need some options in your ~/.xen-osstest/config which you didn't before. The main one is Repos which should point to a scratch directory to use for cloning trees while determining revisions to use. Ian.