From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v8 1/2] OSSTEST: introduce a raisin build test Date: Tue, 4 Aug 2015 10:37:03 +0100 Message-ID: <1438681023.31129.66.camel@citrix.com> References: <1437670366-29034-1-git-send-email-stefano.stabellini@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1437670366-29034-1-git-send-email-stefano.stabellini@eu.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: wei.liu2@citrix.com, ian.jackson@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On Thu, 2015-07-23 at 17:52 +0100, Stefano Stabellini wrote: > > + ./cs-job-create $flight build-$arch-raisin build-raisin \ > + arch=$arch \ > + tree_xen=$TREE_XEN \ > + $RUNVARS $BUILD_RUNVARS $BUILD_RAISIN_RUNVARS $arch_runvars \ > + $suite_runvars \ > + host_hostflags=$build_hostflags \ > + buildjob=${bfi}build-$arch \ This line means you can't run the build-$arch-raisin job unless the build -$arch job is complete. Is that intentional? I can see an argument for not testing raisin if the underlying Xen tree doesn't build, it's a bit annoying in standalone mode is all...