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] [PATCH] Repost - xm lists display and formatting

To: Nivedita Singhvi <niv@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Repost - xm lists display and formatting
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Fri, 17 Feb 2006 14:32:04 -0800
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx, marvel@xxxxxxxxxx, Stefan Berger <stefanb@xxxxxxxxxx>
Delivery-date: Fri, 17 Feb 2006 22:44:45 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43F64CD8.3090106@xxxxxxxxxx>
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>
References: <OF17240851.39237EDD-ON85257118.0078D462-85257118.00793306@xxxxxxxxxx> <43F64CD8.3090106@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Feb 17, 2006 at 02:23:20PM -0800, Nivedita Singhvi wrote:

> Ewan, are you still running xm-test as part of your pre-commit
> regression testing?

Yes, we run the xm-test quick run before the change gets pushed from our
staging tree to xen-unstable, and the xm-test full run overnight (on
many machines).

> Also, have you started running on hvm hw?

James has been working on that recently.  It looks from the XenRT matrix
that it's not there yet, but it certainly will be soon.

> We'd like to see more of these bugs caught prior to commit,
> and hoping to encourage all the developers out there to
> please run as well...

That's what the staging tree is for -- if there was any breakage (which
it turns out that there wasn't) then the change would never have been
pushed to the public unstable tree.  My email was a plea for someone to
improve the comprehensiveness of xm-test, now that we have a new


Xen-devel mailing list