From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu@buildbot.b1-systems.de
Cc: gollub@b1-systems.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] buildbot failure in qemu on s390-next_i386_debian_5_0
Date: Wed, 22 Jun 2011 10:35:21 +0100 [thread overview]
Message-ID: <BANLkTinrubAXa+wLeuqkfSFhpQs1XdL8bQ@mail.gmail.com> (raw)
In-Reply-To: <20110622070301.E1D9D3FC05@buildbot.b1-systems.de>
On Wed, Jun 22, 2011 at 8:03 AM, <qemu@buildbot.b1-systems.de> wrote:
> The Buildbot has detected a new failure on builder s390-next_i386_debian_5_0 while building qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/s390-next_i386_debian_5_0/builds/11
Haven't looked deeply into this but I suspect flaky repo.or.cz.
Probably a temporary issue.
Stefan
next prev parent reply other threads:[~2011-06-22 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 7:03 [Qemu-devel] buildbot failure in qemu on s390-next_i386_debian_5_0 qemu
2011-06-22 9:35 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-03 7:03 qemu
2011-07-19 7: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=BANLkTinrubAXa+wLeuqkfSFhpQs1XdL8bQ@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=gollub@b1-systems.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu@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).