From: qemu@buildbot.b1-systems.de
To: agraf@suse.de, gollub@b1-systems.de, lcapitulino@redhat.com,
qemu-devel@nongnu.org
Subject: [Qemu-devel] buildbot failure in qemu on block_mingw32
Date: Sat, 03 Mar 2012 03:05:01 +0100 [thread overview]
Message-ID: <20120303020502.496743FF0F@buildbot.b1-systems.de> (raw)
The Buildbot has detected a new failure on builder block_mingw32 while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/block_mingw32/builds/144
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_rhel61
Build Reason: The Nightly scheduler named 'nightly_block' triggered this build
Build Source Stamp: [branch block] HEAD
Blamelist:
BUILD FAILED: failed compile
sincerely,
-The Buildbot
next reply other threads:[~2012-03-03 1:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 2:05 qemu [this message]
2012-03-03 9:06 ` [Qemu-devel] buildbot failure in qemu on block_mingw32 Stefan Weil
-- strict thread matches above, loose matches on Subject: below --
2013-01-16 0:06 qemu
2013-01-08 0:06 qemu
2013-01-09 8:53 ` Stefan Hajnoczi
2013-01-09 17:16 ` Stefan Weil
2013-01-10 12:44 ` Stefan Hajnoczi
2013-01-10 13:08 ` Gerd Hoffmann
2012-12-17 0:23 qemu
2012-11-20 0:04 qemu
2012-11-20 13:36 ` Stefan Hajnoczi
2012-11-20 13:49 ` Anthony Liguori
2012-10-24 1:05 qemu
2012-10-24 9:16 ` Kevin Wolf
2012-10-24 11:39 ` Luiz Capitulino
2012-10-20 1:04 qemu
2012-10-22 12:30 ` Kevin Wolf
2012-10-22 13:54 ` Corey Bryant
2012-09-20 6:12 qemu
2012-09-15 1:06 qemu
2012-09-08 1:38 qemu
2012-08-15 1:04 qemu
2012-08-09 1:04 qemu
2012-08-07 1:03 qemu
2012-07-11 1:04 qemu
2012-06-08 1:54 qemu
2012-06-08 9:07 ` Stefan Hajnoczi
2012-06-08 9:51 ` Max Filippov
2012-06-05 1:50 qemu
2012-05-10 1:04 qemu
2012-05-10 7:28 ` Paolo Bonzini
2012-04-04 1:43 qemu
2012-02-20 6:44 qemu
2012-01-24 2:05 qemu
2011-12-16 2:06 qemu
2011-11-23 2:04 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=20120303020502.496743FF0F@buildbot.b1-systems.de \
--to=qemu@buildbot.b1-systems.de \
--cc=agraf@suse.de \
--cc=gollub@b1-systems.de \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.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 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).