From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com, wei.liu2@citrix.com
Subject: Re: [xen-unstable test] 62004: regressions - FAIL
Date: Thu, 17 Sep 2015 10:08:23 -0600 [thread overview]
Message-ID: <55FAE577.9090400@suse.com> (raw)
In-Reply-To: <1442473629.24382.135.camel@citrix.com>
On 09/17/2015 01:07 AM, Ian Campbell wrote:
> On Thu, 2015-09-17 at 01:22 +0000, osstest service owner wrote:
>> flight 62004 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/62004/
>>
>> test-amd64-amd64-libvirt-pair pass
>> test-amd64-i386-libvirt-pair pass
> Although the overall flight failed these two are the first pass of the
> libvirt migration tests after the recent fixed went in to osstest and
> libxl.
>
> Looks like xen-4.6-testing is already passing too (flight 62015).
Good to hear! Thanks for all your work on this!
Regards,
Jim
prev parent reply other threads:[~2015-09-17 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 1:22 [xen-unstable test] 62004: regressions - FAIL osstest service owner
2015-09-17 7:07 ` Ian Campbell
2015-09-17 16:08 ` Jim Fehlig [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=55FAE577.9090400@suse.com \
--to=jfehlig@suse.com \
--cc=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 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).