This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Testing the kernels

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Testing the kernels
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 31 Aug 2010 16:06:20 +0100
Cc: "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 31 Aug 2010 08:08:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C75943A.2000909@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <4C75943A.2000909@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Jeremy Fitzhardinge writes ("[Xen-devel] Testing the kernels"):
> I think you should use "xen/next-2.6.32" as the input to the test
> subsystem.  If you have a git tree on xenbits with a, say,
> "xen/tested-2.6.32" branch which gets updated when the tests pass,

I have done roughly this.  It seems to be mostly working[1] after I
told it to do some tests over the weekend, so I've reenabled it for
emailing to the list.

[1] When I say working I mean that the test system is functioning
properly.  Unfortunately many of the tests themselves are failing.

The tested tree is:
branch "master".

I can switch the tester's input at will.  Can you promise that when we
do that, all updates will be fast forwards, so that the tested output
branch is always fast forwarding ?

>  then I can make that automatically update xen/stable-2.6.32.x for
> public consumption.

Can this be done in a way that doesn't involve waiting for you ?  The
testing system obviously pushes automatically and it would be good to
publish those things in the right places without further manual

Also, you'll see that I chose a single branch name "master" rather
than encoding the kernel version number.  This is because I think we
should have one branch tested like this, rather than a separate branch
for each kernel version.

When we update the kernel version we intend to use, this should be a
fast forward update and gated though the testing in the ordinary way,
so it should update the same tag.  Do you agree ?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>