From: qemu-kvm@buildbot.b1-systems.de
To: gollub@b1-systems.de, kvm@vger.kernel.org
Subject: buildbot failure in qemu-kvm on default_i386_debian_5_0
Date: Mon, 21 Sep 2009 11:53:57 +0200 [thread overview]
Message-ID: <20090921095357.43859BF71@buildbot.b1-systems.de> (raw)
The Buildbot has detected a new failure of default_i386_debian_5_0 on qemu-kvm.
Full details are available at:
http://buildbot.b1-systems.de/qemu-kvm/builders/default_i386_debian_5_0/builds/75
Buildbot URL: http://buildbot.b1-systems.de/qemu-kvm/
Buildslave for this Build: b1_qemu_kvm_2
Build Reason:
Build Source Stamp: [branch master] HEAD
Blamelist: Anthony Liguori <aliguori@us.ibm.com>,Aurelien Jarno <aurelien@aurel32.net>,Avi Kivity <avi@redhat.com>,Blue Swirl <blauwirbel@gmail.com>,Christoph Hellwig <hch@lst.de>,Daniel Jacobowitz <drow@false.org>,Dustin Kirkland <kirkland@canonical.com>,Edgar E. Iglesias <edgar.iglesias@gmail.com>,Gerd Hoffmann <kraxel@redhat.com>,Gleb Natapov <gleb@redhat.com>,Huang Ying <ying.huang@intel.com>,Jan Kiszka <jan.kiszka@siemens.com>,Jan Kiszka <jan.kiszka@web.de>,Jim Paris <jim@jtan.com>,Juan Quintela <quintela@redhat.com>,Kevin Wolf <kwolf@redhat.com>,Kirill A. Shutemov <kirill@shutemov.name>,Marcelo Tosatti <mtosatti@redhat.com>,Markus Armbruster <armbru@redhat.com>,Michael S. Tsirkin <mst@redhat.com>,Reimar Döffinger <Reimar.Doeffinger@gmx.de>,Sebastian Herbszt <herbszt@gmx.de>,Stefan Weil <weil@mail.berlios.de>,Yan Vugenfirer <yvugenfi@redhat.com>,malc <av1474@comtv.ru>
BUILD FAILED: failed compile
sincerely,
-The Buildbot
next reply other threads:[~2009-09-21 9:52 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 9:53 qemu-kvm [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-05 2:03 buildbot failure in qemu-kvm on default_i386_debian_5_0 qemu-kvm
2011-11-09 2:07 qemu-kvm
2011-09-08 1:03 qemu-kvm
2011-07-01 1:05 qemu-kvm
2011-02-04 2:05 qemu-kvm
2010-12-22 2:23 qemu-kvm
2010-12-05 11:04 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:28 qemu-kvm
2010-11-25 11:53 qemu-kvm
2010-11-23 13:02 qemu-kvm
2010-11-02 2:03 qemu-kvm
2010-10-04 1:04 qemu-kvm
2010-09-22 1:03 qemu-kvm
2010-08-28 1:04 qemu-kvm
2010-07-26 1:03 qemu-kvm
2010-05-17 10:32 qemu-kvm
2010-04-19 14:56 qemu-kvm
2010-03-19 2:06 qemu-kvm
2010-02-25 12:26 qemu-kvm
2010-02-21 12:55 qemu-kvm
2010-02-17 16:32 qemu-kvm
2009-12-19 2:03 qemu-kvm
2009-12-16 2:03 qemu-kvm
2009-12-14 16:40 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-16 15:28 qemu-kvm
2009-11-15 10:09 qemu-kvm
2009-11-02 13:37 qemu-kvm
2009-10-26 13:24 qemu-kvm
2009-10-25 9:44 qemu-kvm
2009-10-15 1:03 qemu-kvm
2009-10-09 1:04 qemu-kvm
2009-10-07 9:25 qemu-kvm
2009-10-06 9:14 qemu-kvm
2009-10-05 15:09 qemu-kvm
2009-08-31 11:21 qemu-kvm
2009-08-31 11:28 ` Daniel Gollub
2009-08-31 12:25 ` Avi Kivity
2009-07-29 8:10 qemu-kvm
2009-07-29 12:08 ` Daniel Gollub
2009-07-28 14:01 qemu-kvm
2009-07-28 1:03 qemu-kvm
[not found] <20090727093315.AF030BF78@buildbot.b1-systems.de>
2009-07-27 10:02 ` Daniel Gollub
2009-07-27 9:33 qemu-kvm
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=20090921095357.43859BF71@buildbot.b1-systems.de \
--to=qemu-kvm@buildbot.b1-systems.de \
--cc=gollub@b1-systems.de \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.