From: Stefan Weil <weil@mail.berlios.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
gollub@b1-systems.de, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] buildbot failure in qemu on xen_x86_64_debian_5_0
Date: Thu, 07 Jul 2011 07:19:03 +0200 [thread overview]
Message-ID: <4E1541C7.9060400@mail.berlios.de> (raw)
In-Reply-To: <20110707050349.C27C2BF74@buildbot.b1-systems.de>
Am 07.07.2011 07:03, schrieb qemu@buildbot.b1-systems.de:
> The Buildbot has detected a new failure on builder
> xen_x86_64_debian_5_0 while building qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/xen_x86_64_debian_5_0/builds/26
>
> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>
> Buildslave for this Build: b1_qemu_1
>
> Build Reason: The Nightly scheduler named 'nightly_xen' triggered this
> build
> Build Source Stamp: [branch xen-next] HEAD
> Blamelist:
>
> BUILD FAILED: failed compile
>
> sincerely,
> -The Buildbot
>
This patch fixes compilation for Debian Lenny based buildbots:
http://patchwork.ozlabs.org/patch/103157/.
Maybe someone can apply the patch (or provide a different
solution) to stop those repeated buildbot mails and fix the
build breakage.
Is it possible to configure the buildbots to send a mail only
when the status changes (good -> bad, bad -> good)?
Thanks and kind regards,
Stefan Weil
next prev parent reply other threads:[~2011-07-07 5:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 5:03 [Qemu-devel] buildbot failure in qemu on xen_x86_64_debian_5_0 qemu
2011-07-07 5:19 ` Stefan Weil [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-07 5:03 qemu
2011-07-31 5:03 qemu
2011-07-26 5:03 qemu
2011-07-19 5:03 qemu
2011-07-04 5:04 qemu
2011-07-01 5:03 qemu
2011-06-12 5:03 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=4E1541C7.9060400@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--cc=gollub@b1-systems.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).