From mboxrd@z Thu Jan  1 00:00:00 1970
From: George Dunlap <george.dunlap@eu.citrix.com>
Subject: Re: [PATCH v4] OSSTEST: introduce a raisin build test
Date: Mon, 18 May 2015 14:23:52 +0100
Message-ID: <5559E7E8.50207@eu.citrix.com>
References: <1431422408-16659-1-git-send-email-stefano.stabellini@eu.citrix.com>
	<1431425547.8263.127.camel@citrix.com>
	<alpine.DEB.2.02.1505121202050.20496@kaball.uk.xensource.com>
	<1431430431.8263.143.camel@citrix.com>
	<alpine.DEB.2.02.1505121243010.20496@kaball.uk.xensource.com>
	<1431507683.8263.212.camel@citrix.com>
	<alpine.DEB.2.02.1505131247430.20496@kaball.uk.xensource.com>
	<CAFLBxZYpyq-bvsMVTYuPFTp2ro192JqZsw8LsgJPm4Tqe7=row@mail.gmail.com>
	<1431945198.4944.30.camel@citrix.com> <5559C4D7.70200@eu.citrix.com>
	<1431948085.4944.48.camel@citrix.com> <5559E3B4.7010707@eu.citrix.com>
	<1431954864.4944.57.camel@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1431954864.4944.57.camel@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Wei Liu <wei.liu2@citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 05/18/2015 02:14 PM, Ian Campbell wrote:
>> That solves the most general case; but it sounds like you care mostly
>> about the very specific case of dealing with components that depend on
>> the current output of xen.git.  Starting simple may be fine.
> 
> Currently we only have ts-*-build things which depend on the output of
> ts-xen-build (in fact, we only have ts-libvirt-build).
> 
> I'm not sure if there will be others in the future, I suppose
> ts-rump{qemu,xenstore,foo}-build -> ts-rumpkernel-build -> ts-xen-build
> might eventually be a possibility...

I guess I was assuming that at some point you might have the following
builds and dependencies (not sure these are all correct):
 ts-seabios-build: [none]
 ts-qemut-build: [none]
 ts-qemuu-build: ts-seabios-build
 ts-xen-build: ts-qemut-build ts-qemuu-build
 ts-libvirt-build: ts-xen-build
 &c

I'm not arguing for this, I'm just trying to explain the problem I was
initially trying to solve. :-)

But as we don't have any tests for seabios and qemu* in isolation, I
guess it doesn't really make sense to treat them separately.

 -George