Ian Campbell wrote:
> On Mon, 2015-01-19 at 09:37 +, Ian Campbell wrote:
>
>> On Mon, 2015-01-19 at 04:48 +, xen.org wrote:
>>
>>> branch xen-unstable
>>> xen branch xen-unstable
>>> job build-armhf-libvirt
>>> test libvirt-build
>>>
>>> Tree: libvirt git://libvirt.org/libvirt.git
>
On Mon, 2015-01-19 at 09:37 +, Ian Campbell wrote:
> On Mon, 2015-01-19 at 04:48 +, xen.org wrote:
> > branch xen-unstable
> > xen branch xen-unstable
> > job build-armhf-libvirt
> > test libvirt-build
> >
> > Tree: libvirt git://libvirt.org/libvirt.git
> > Tree: qemuu git://xenbits.xen.or
On Tue, 2014-09-09 at 09:54 +0100, Daniel P. Berrange wrote:
> On Tue, Sep 09, 2014 at 09:49:47AM +0100, Ian Campbell wrote:
> > Xen's automated testing of libvirt against newer Xen's has found a build
> > issue which it has bisected down to "blockcopy: expose new API in
> > virsh".
> >
> > An ins
On Tue, Sep 09, 2014 at 09:49:47AM +0100, Ian Campbell wrote:
> Xen's automated testing of libvirt against newer Xen's has found a build
> issue which it has bisected down to "blockcopy: expose new API in
> virsh".
>
> An instance of the failure can be found in flight 30154:
> http://lists.xen.org
On 09/09/2014 10:49 AM, Ian Campbell wrote:
> Xen's automated testing of libvirt against newer Xen's has found a build
> issue which it has bisected down to "blockcopy: expose new API in
> virsh".
>
> An instance of the failure can be found in flight 30154:
> http://lists.xen.org/archives/html/xen
Xen's automated testing of libvirt against newer Xen's has found a build
issue which it has bisected down to "blockcopy: expose new API in
virsh".
An instance of the failure can be found in flight 30154:
http://lists.xen.org/archives/html/xen-devel/2014-09/msg01063.html
links to the logs =
