From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Stefan Weil <sw@weilnetz.de>, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_mingw32
Date: Tue, 07 Feb 2012 09:32:59 -0500 [thread overview]
Message-ID: <4F31361B.7040300@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAJSP0QU0gtLhY-vK_xN0bv2twHgA_yC+9zLB+6QK97B2Bo4DiQ@mail.gmail.com>
On 02/07/2012 05:28 AM, Stefan Hajnoczi wrote:
> On Mon, Feb 6, 2012 at 8:27 PM, Corey Bryant<coreyb@linux.vnet.ibm.com> wrote:
>>
>>
>> On 02/04/2012 03:29 AM, Stefan Weil wrote:
>>>
>>> Am 04.02.2012 00:43, schrieb Anthony Liguori:
>>>>
>>>> On 02/03/2012 06:11 PM, qemu@buildbot.b1-systems.de wrote:
>>>>>
>>>>> The Buildbot has detected a new failure on builder default_mingw32
>>>>> while building qemu.
>>>>> Full details are available at:
>>>>> http://buildbot.b1-systems.de/qemu/builders/default_mingw32/builds/167
>>>>>
>>>>> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>>>>>
>>>>> Buildslave for this Build: kraxel_rhel61
>>>>>
>>>>> Build Reason: The Nightly scheduler named 'nightly_default' triggered
>>>>> this build
>>>>> Build Source Stamp: [branch master] HEAD
>>>>> Blamelist:
>>>>>
>>>>> BUILD FAILED: failed compile
>>>>
>>>>
>>>> Hi Corey,
>>>>
>>>> This came in through your net bridge helper series. Can you send a
>>>> patch for this? Stefan Weil may be able to help you figure out what's
>>>> needed here for win32.
>>>>
>>>> Regards,
>>>>
>>>> Anthony Liguori
>>>
>>>
>>> Hi,
>>>
>>> removing the bridge code for hosts which don't support it (quote from
>>> Corey's commit: "this is very Linux centric")
>>> seems currently the best solution. I just sent a patch which does this
>>> for w32 hosts. Maybe BSD also should be
>>> added.
>>>
>>> Regards,
>>>
>>> Stefan Weil
>>>
>>>
>>
>> Who can I talk to about BSD?
>
> Are you looking for someone to test BSD or are you volunteering to add
> a BSD build slave?
>
> If you want to add a BSD build slave to the buildbot, please email
> Daniel Gollub<gollub@b1-systems.de>. You can find out more
> information here:
> http://wiki.qemu.org/ContinuousIntegration
>
> Stefan
>
Thanks. I'm more concerned with breaking a BSD build. I'm not a BSD
guy. It looks like BSD doesn't have unique net_init_* functions so I
don't think they'll get an "undefined reference to `net_init_bridge'"
compile error like win32.
Someone to test would be great too though! :) I'm not familiar with how
this typically works. I assume they'll pick it up eventually and try it
out.
--
Regards,
Corey
next prev parent reply other threads:[~2012-02-07 14:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 0:11 [Qemu-devel] buildbot failure in qemu on default_mingw32 qemu
2012-02-03 23:43 ` Anthony Liguori
2012-02-04 8:29 ` Stefan Weil
2012-02-06 20:27 ` Corey Bryant
2012-02-07 10:28 ` Stefan Hajnoczi
2012-02-07 14:32 ` Corey Bryant [this message]
2012-02-07 14:59 ` Stefan Hajnoczi
2012-02-07 15:10 ` Corey Bryant
-- strict thread matches above, loose matches on Subject: below --
2013-01-18 22:27 qemu
2013-01-14 22:23 qemu
2013-01-03 22:51 qemu
2012-11-16 22:48 qemu
2012-11-17 7:28 ` Stefan Weil
2012-11-03 1:11 qemu
2012-11-03 6:08 ` Stefan Hajnoczi
2012-11-03 9:24 ` Daniel Gollub
2012-11-03 14:35 ` Stefan Hajnoczi
2012-10-30 0:53 qemu
2012-10-30 8:03 ` Paolo Bonzini
2012-10-30 14:05 ` Michael S. Tsirkin
2012-10-05 23:51 qemu
2012-10-08 6:07 ` Stefan Hajnoczi
2012-09-10 23:54 qemu
2012-09-11 5:14 ` Stefan Weil
2012-09-11 5:23 ` Stefan Weil
2012-09-11 6:57 ` Paolo Bonzini
2012-09-11 7:05 ` Zhang, Yang Z
2012-09-11 7:07 ` Paolo Bonzini
2012-09-11 7:15 ` Zhang, Yang Z
2012-09-06 0:06 qemu
2012-09-06 0:22 ` Max Filippov
2012-08-14 23:32 qemu
2012-08-06 23:26 qemu
2012-08-03 23:29 qemu
2012-07-19 23:18 qemu
2012-07-17 23:10 qemu
2012-07-09 23:47 qemu
2012-03-15 0:32 qemu
2012-03-01 0:36 qemu
2012-03-01 0:35 ` Roy Tam
2011-12-13 1:02 qemu
2011-12-13 6:33 ` Paolo Bonzini
2011-10-03 23:29 qemu
2011-09-30 23:06 qemu
2011-09-20 23:28 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=4F31361B.7040300@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=sw@weilnetz.de \
/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).