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] Daily Xen Builds

To: "Anthony Liguori" <aliguori@xxxxxxxxxx>, "David F Barrera" <dfbp@xxxxxxxxxx>
Subject: RE: [Xen-devel] Daily Xen Builds
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 11 Oct 2005 16:10:29 +0100
Cc: Dan Smith <danms@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 11 Oct 2005 15:07:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXN4JlkIHjz3p6xQauSQwYUQxt7fgAhfFMQ
Thread-topic: [Xen-devel] Daily Xen Builds
> Is it perhaps wise, nearing 3.0, that we adopt a policy of 
> running the various test suites on code before it gets pushed 
> to the public tree?  
> This seems like requiring passing on xm-test a sane thing to 
> do for the tools related changes.  Is there anything that 
> needs to be done to the test suites to make this less painful 
> for the committers?

We've been working towards getting XenRT integrated in our changeset
release system, and are hoping to go live in the next couple of days.
It's a shame we didn't have it for yesterday's hickup, but too bad.

Every check-in will automatically trigger a run of the XenRT 'fast' test
suite. This will result in it being built, booted, and undergoing
various tests (including xm-test). Only changesets that pass on all of
x86_32, x86_32p and x86_64 will be pushed out from the staging area to
the public xenbits.xensource.com repository. The fast test suite takes
about one hour to run.

This should put an end to changesets that have obvious faults escaping
into the wild. 

The longer XenRT test suites will still be run on every nightly snapshot
(and reported to xenbits.xensource.com/xenrt)


Xen-devel mailing list