From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xensource.com,
osstest service owner <osstest-admin@xenproject.org>
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 [thread overview]
Message-ID: <1441630156.25589.115.camel@citrix.com> (raw)
In-Reply-To: <20150907124353.GH6436@zion.uk.xensource.com>
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.
next prev parent reply other threads:[~2015-09-07 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 16:49 [xen-unstable test] 61379: trouble: blocked/broken osstest service owner
2015-09-07 11:55 ` osstest breakage, now believed fixed (Was: Re: [xen-unstable test] 61379: trouble: blocked/broken) Ian Campbell
2015-09-07 12:43 ` Wei Liu
2015-09-07 12:49 ` Ian Campbell [this message]
2015-09-07 13:03 ` Wei Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1441630156.25589.115.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.