From: Ian Campbell <Ian.Campbell@citrix.com>
To: "xen.org" <Ian.Jackson@eu.citrix.com>, Jim Fehlig <jfehlig@suse.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [libvirt test] 36071: tolerable all pass - PUSHED
Date: Wed, 11 Mar 2015 08:51:16 +0000 [thread overview]
Message-ID: <1426063876.28029.22.camel@citrix.com> (raw)
In-Reply-To: <osstest-36071-mainreport@xen.org>
On Tue, 2015-03-10 at 17:59 +0000, xen.org wrote:
> flight 36071 libvirt real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/36071/
>
> Failures :-/ but no regressions.
>
> Tests which did not succeed, but are not blocking:
> test-armhf-armhf-libvirt 10 migrate-support-check fail never pass
> test-amd64-amd64-libvirt 10 migrate-support-check fail never pass
> test-amd64-i386-libvirt 10 migrate-support-check fail never pass
>
> version targeted for testing:
> libvirt b39b1397ea6e6155b5e363d456196504093edd07
> baseline version:
> libvirt 719cd2182bf06196b26204a8cf88d28001b1d79b
This range contains a trio of libxl fixes:
$ git log --oneline 719cd2182bf06196b26204a8cf88d28001b1d79b..b39b1397ea6e6155b5e363d456196504093edd07 | grep libxl
3b7f589 libxl: remove unneeded cleanup_unlock label
b1d159d libxl: use libxl_ctx passed to libxlConsoleCallback
fc3ef44 libxl: remove redundant calls to libxl_evdisable_domain_death
Were any of them expected to resolve the libvirtd disappears issue which
we've been suffering lately or is this just a lucky pass?
I suppose we should monitor things for a few flights and then consider
removing the all.allow entry which makes libvirt failures non-blocking
in all other branches.
Ian.
next prev parent reply other threads:[~2015-03-11 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 17:59 [libvirt test] 36071: tolerable all pass - PUSHED xen.org
2015-03-11 8:51 ` Ian Campbell [this message]
2015-03-11 14:17 ` Jim Fehlig
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=1426063876.28029.22.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jfehlig@suse.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.