qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, agraf@suse.de,
	qemu@buildbot.b1-systems.de, gollub@b1-systems.de,
	lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on block_x86_64_debian_6_0
Date: Tue, 24 Jan 2012 09:53:05 +0100	[thread overview]
Message-ID: <4F1E7171.4060908@redhat.com> (raw)
In-Reply-To: <4F1E5579.3070202@suse.de>

Am 24.01.2012 07:53, schrieb Andreas Färber:
> Am 24.01.2012 04:12, schrieb qemu@buildbot.b1-systems.de:
>> The Buildbot has detected a new failure on builder block_x86_64_debian_6_0 while building qemu.
>> Full details are available at:
>>  http://buildbot.b1-systems.de/qemu/builders/block_x86_64_debian_6_0/builds/162
>>
>> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>>
>> Buildslave for this Build: yuzuki
>>
>> Build Reason: The Nightly scheduler named 'nightly_block' triggered this build
>> Build Source Stamp: [branch block] HEAD
>> Blamelist: 
>>
>> BUILD FAILED: failed compile
> 
> Log says:
> 
>   CC    blockdev.o
> cc1: warnings being treated as errors
> blockdev.c: In function 'eject_device':
> blockdev.c:715: error: 'return' with a value, in function returning void
> make[1]: Leaving directory `/home/build/qemu/block_x86_64_debian_6_0/build'
> make[1]: *** [blockdev.o] Error 1

Stefan, this seems to be a merge conflict for your patch "block: check
bdrv_in_use() before blockdev operations". I'll apply this fix to the patch:

diff --git a/blockdev.c b/blockdev.c
index 9252c25..0499ee6 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -678,8 +678,8 @@ void qmp_blockdev_snapshot_sync(const char *device,
const char *snapshot_file,
 static void eject_device(BlockDriverState *bs, int force, Error **errp)
 {
     if (bdrv_in_use(bs)) {
-        qerror_report(QERR_DEVICE_IN_USE, bdrv_get_device_name(bs));
-        return -1;
+        error_set(errp, QERR_DEVICE_IN_USE, bdrv_get_device_name(bs));
+        return;
     }
     if (!bdrv_dev_has_removable_media(bs)) {
         error_set(errp, QERR_DEVICE_NOT_REMOVABLE,
bdrv_get_device_name(bs));

Kevin

  reply	other threads:[~2012-01-24  8:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24  3:12 [Qemu-devel] buildbot failure in qemu on block_x86_64_debian_6_0 qemu
2012-01-24  6:53 ` Andreas Färber
2012-01-24  8:53   ` Kevin Wolf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-11  0:05 qemu
2012-09-20  6:29 qemu
2012-08-15  4:00 qemu
2012-06-05  2:50 qemu
2012-03-17  3:12 qemu
2012-01-13  2:10 qemu
2011-11-23  3:20 qemu
2011-11-23  8:34 ` Stefan Hajnoczi
2011-11-23  8:41   ` Stefan Hajnoczi
2011-11-23  8:45   ` Kevin Wolf
2011-11-01  5:34 qemu
2011-10-06  2:16 qemu
2011-09-20  1:53 qemu
2011-09-14  2:08 qemu
2011-09-03  1:20 qemu

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=4F1E7171.4060908@redhat.com \
    --to=kwolf@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=gollub@b1-systems.de \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu@buildbot.b1-systems.de \
    --cc=stefanha@linux.vnet.ibm.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).