WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Daily Xen Builds

To: David F Barrera <dfbp@xxxxxxxxxx>
Subject: Re: [Xen-devel] Daily Xen Builds
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Mon, 10 Oct 2005 16:21:25 -0500
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Dan Smith <danms@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Oct 2005 21:18:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1128978545.12366.15.camel@dbarrera_tp>
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: <1128978545.12366.15.camel@dbarrera_tp>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050912)
David F Barrera wrote:

Test changeset:

changeset:   7293:0f33cbec4e36
tag:         tip
user:        emellor@ewan
date:        Mon Oct 10 13:06:14 2005 +0100
summary:     This patch fixes an error in the xm create path when the

Last known good changeset for all platforms: 7069:a172340ae3f3
<snip>

xm-test: This suite provides a framework for testing the Xen userspace
tools.

SUMMARY:
           Platform | PASS | FAIL | XPASS | XFAIL |
---------------------+------+------+-------+-------+
             FC3pae |   64 |   30 |     0 |     1 |
hs20.1.sles9-x86_64 |   62 |   32 |     0 |     1 |
hs20.2.sles9-x86_64 |   62 |   32 |     0 |     1 |
    hs20.fc4_x86_64 |   63 |   31 |     0 |     1 |
    x235sles9nonpae |   64 |   28 |     0 |     1 |
         x305rh4pae |   63 |   30 |     0 |     1 |
         x335fc4pae |   53 |   39 |     0 |     1 |

This is a lot of failures.

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?

Just to clarify, I'm suggesting that all changes should be checked (external patches or Cambridge pushes) against the testsuites before committing. Just seems like it would be a good way to ensure that we avoid regressing as we near 3.0 release.

I don't think anyone is particularly at fault for the recent regressions, I just think it's time we adopt a more rigorious commit policy.

Thoughts?

Regards,

Anthony Liguori

-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel