On Tue, 4 Aug 2015, Ian Campbell wrote:
> 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...
Fair enough. I can remove the buildjob=${bfi}build-$arch line.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
