From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: osstest breakage,
 now believed fixed (Was: Re: [xen-unstable test] 61379: trouble:
 blocked/broken)
Date: Mon, 7 Sep 2015 13:49:16 +0100
Message-ID: <1441630156.25589.115.camel@citrix.com>
References: <osstest-61379-mainreport@xen.org>
	<1441626925.25589.103.camel@citrix.com>
	<20150907124353.GH6436@zion.uk.xensource.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: <20150907124353.GH6436@zion.uk.xensource.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: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xensource.com, osstest service owner <osstest-admin@xenproject.org>
List-Id: xen-devel@lists.xenproject.org

On Mon, 2015-09-07 at 13:43 +0100, Wei Liu wrote:
> On Mon, Sep 07, 2015 at 12:55:25PM +0100, Ian Campbell wrote:
> > On Sun, 2015-09-06 at 16:49 +0000, osstest service owner wrote:
> > > flight 61379 xen-unstable real [real]
> > > http://logs.test-lab.xenproject.org/osstest/logs/61379/
> > > 
> > > Failures and problems with tests :-(
> > > 
> > > Tests which did not succeed and are blocking,
> > > including tests which could not be run:
> > >  build-armhf                   3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-armhf-xsm               3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-amd64-oldkern           3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-amd64-prev              3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-i386-oldkern            3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-amd64-xsm               3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-amd64-pvops             3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-i386-prev               3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-i386-pvops              3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-i386                    3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-i386-xsm                3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-amd64                   3 host-install(3)         broken REGR. 
> > > vs. 61059
> > >  build-armhf-pvops             3 host-install(3)         broken REGR. 
> > > vs. 61059
> > 
> > The cache/proxy had gotten itself into some weird state and was giving 
> > 404
> > for URLs which did in fact exist and which were insisted upon by the 
> > Debian
> > Installer.
> > 
> > Ian and I investigated a bit and the cache process has now been 
> > restarted
> > and seems to be running fine now. Flights will restart in the normal 
> > way.
> > 
> 
> I believe it's going to pick up the latest xen-unstable staging?

Flight 61521 seems to have picked up on a7b39c8bd6cb, yes.

Ian.