From: Avi Kivity <avi@redhat.com>
To: Daniel Gollub <gollub@b1-systems.de>
Cc: qemu-kvm@buildbot.b1-systems.de, kvm@vger.kernel.org
Subject: Re: buildbot failure in qemu-kvm on default_x86_64_debian_5_0
Date: Mon, 31 Aug 2009 16:27:35 +0300 [thread overview]
Message-ID: <4A9BCFC7.4020207@redhat.com> (raw)
In-Reply-To: <200908311524.53671.gollub@b1-systems.de>
On 08/31/2009 04:24 PM, Daniel Gollub wrote:
> On Monday 31 August 2009 03:17:04 pm qemu-kvm@buildbot.b1-systems.de wrote:
>
>> The Buildbot has detected a new failure of default_x86_64_debian_5_0 on
>> qemu-kvm. Full details are available at:
>> http://buildbot.b1-systems.de/qemu-kvm/builders/default_x86_64_debian_5_0/
>> builds/38
>>
>>
> "fatal: The remote end hung up unexpectedly"
>
> Thats new ... or also related to the rsync-problem?
>
> The other 3 buildslaves succeeded in doing git-fetch ...
>
>
Could be a transient error.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-31 13:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090831131704.AEB65BF71@buildbot.b1-systems.de>
2009-08-31 13:24 ` buildbot failure in qemu-kvm on default_x86_64_debian_5_0 Daniel Gollub
2009-08-31 13:27 ` Avi Kivity [this message]
2013-03-05 2:03 qemu-kvm
-- strict thread matches above, loose matches on Subject: below --
2011-11-09 2:06 qemu-kvm
2011-11-09 9:47 ` Stefan Hajnoczi
2011-09-08 1:03 qemu-kvm
2011-07-01 1:05 qemu-kvm
2010-12-05 11:03 qemu-kvm
2010-12-04 21:06 qemu-kvm
2010-12-02 10:00 qemu-kvm
2010-11-30 18:38 qemu-kvm
2010-11-29 16:27 qemu-kvm
2010-11-25 11:52 qemu-kvm
2010-11-23 13:00 qemu-kvm
2010-05-17 10:32 qemu-kvm
2010-05-23 9:04 ` Avi Kivity
2010-04-08 1:03 qemu-kvm
2010-02-25 12:26 qemu-kvm
2010-02-17 16:31 qemu-kvm
2009-12-19 2:03 qemu-kvm
2009-12-23 10:00 ` Avi Kivity
2009-12-23 10:01 ` Daniel Gollub
2009-12-23 11:11 ` Daniel Gollub
2009-12-23 12:50 ` Avi Kivity
2009-12-16 2:03 qemu-kvm
2009-12-14 16:39 qemu-kvm
2009-12-13 17:56 qemu-kvm
2009-12-10 14:15 qemu-kvm
2009-11-19 16:37 qemu-kvm
2009-11-15 13:32 qemu-kvm
2009-10-26 13:24 qemu-kvm
2009-10-25 9:38 qemu-kvm
2009-10-24 1:06 qemu-kvm
2009-10-15 1:03 qemu-kvm
2009-10-06 9:11 qemu-kvm
2009-09-28 1:03 qemu-kvm
2009-09-21 9:54 qemu-kvm
2009-08-31 13:17 qemu-kvm
2009-08-31 11:21 qemu-kvm
2009-07-29 8:10 qemu-kvm
2009-07-28 14:01 qemu-kvm
2009-07-27 9:33 qemu-kvm
2009-07-26 14:26 qemu-kvm
2009-07-26 15:14 ` Avi Kivity
2009-07-26 15:13 ` Daniel Gollub
2009-07-26 15:14 ` Daniel Gollub
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=4A9BCFC7.4020207@redhat.com \
--to=avi@redhat.com \
--cc=gollub@b1-systems.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-kvm@buildbot.b1-systems.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).