From: "Jan Beulich" <JBeulich@suse.com>
To: ian.jackson@eu.citrix.com
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-4.4-testing test] 30201: regressions - FAIL
Date: Thu, 11 Sep 2014 08:18:50 +0100 [thread overview]
Message-ID: <541168FA0200007800033AA2@mail.emea.novell.com> (raw)
In-Reply-To: <osstest-30201-mainreport@xen.org>
>>> On 10.09.14 at 23:35, <Ian.Jackson@eu.citrix.com> wrote:
> flight 30201 xen-4.4-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/30201/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-i386-xl-win7-amd64 7 windows-install fail REGR. vs. 30090
Hmm, this is the second failure in a row, yet the guest appears to
be up and running, and at least I can't (once again) spot anything
odd in the logs. And together with considering that all other tests
worked fine, a networking issue also doesn't seem likely.
Jan
prev parent reply other threads:[~2014-09-11 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 21:35 [xen-4.4-testing test] 30201: regressions - FAIL xen.org
2014-09-11 7:18 ` Jan Beulich [this message]
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=541168FA0200007800033AA2@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).