xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: libvir-list@redhat.com, keir@xen.org,
	xen-devel@lists.xensource.com,
	"xen.org" <Ian.Jackson@eu.citrix.com>,
	stefano.stabellini@eu.citrix.com
Subject: Re: [libvirt] [libvirt bisection] complete build-armhf-libvirt
Date: Tue, 9 Sep 2014 09:54:18 +0100	[thread overview]
Message-ID: <20140909085418.GB27589@redhat.com> (raw)
In-Reply-To: <1410252587.8217.35.camel@kazak.uk.xensource.com>

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/archives/html/xen-devel/2014-09/msg01063.html
> 	links to the logs =>
> http://www.chiark.greenend.org.uk/~xensrcts/logs/30154/
> 	click the header of a failing column =>
> http://www.chiark.greenend.org.uk/~xensrcts/logs/30154/build-armhf-libvirt/info.html 
> 	click the failing step =>
> http://www.chiark.greenend.org.uk/~xensrcts/logs/30154/build-armhf-libvirt/5.ts-libvirt-build.log
> 
>         virsh-domain.c: In function 'cmdBlockCopy':
>         virsh-domain.c:2003:17: error: comparison is always false due to limited range of data type [-Werror=type-limits]
>         cc1: all warnings being treated as errors
> 
> It seems to be failing similarly on i386 and I suppose most 32-bit
> arches.

Thanks, we've just had a fix for that pushed

  commit efe5061f5a61d04b1bf21fcac2919a2325f54150
  Author: Eric Blake <eblake@redhat.com>
  Date:   Mon Sep 8 08:50:48 2014 -0600

    blockjob: avoid 32-bit compilation warning
    
    Commit c1d75de caused this warning on 32-bit platforms (fatal when
    -Werror is enabled):
    
    virsh-domain.c: In function 'cmdBlockCopy':
    virsh-domain.c:2003:17: error: comparison is always false due to limited range of data type [-Werror=type-
    
    Forcing the left side of the < to be ull instead of ul shuts up
    the 32-bit compiler while still protecting 64-bit code from overflow.
    

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2014-09-09  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 18:30 [libvirt bisection] complete build-armhf-libvirt xen.org
2014-09-09  8:49 ` [libvirt] [Xen-devel] " Ian Campbell
2014-09-09  8:54   ` Daniel P. Berrange [this message]
2014-09-09  9:01     ` Ian Campbell
2014-09-09  8:55   ` Ján Tomko

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=20140909085418.GB27589@redhat.com \
    --to=berrange@redhat.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=libvir-list@redhat.com \
    --cc=stefano.stabellini@eu.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).