qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: qemu@buildbot.b1-systems.de, agraf@suse.de, gollub@b1-systems.de,
	lcapitulino@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] buildbot failure in qemu on virtfs_x86_64_debian_6_0
Date: Sun, 29 Jan 2012 22:28:40 +0530	[thread overview]
Message-ID: <87k44amon3.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120129090658.496753FC6C@buildbot.b1-systems.de>

On Sun, 29 Jan 2012 10:06:58 +0100, qemu@buildbot.b1-systems.de wrote:
> The Buildbot has detected a new failure on builder virtfs_x86_64_debian_6_0 while building qemu.
> Full details are available at:
>  http://buildbot.b1-systems.de/qemu/builders/virtfs_x86_64_debian_6_0/builds/0
> 
> Buildbot URL: http://buildbot.b1-systems.de/qemu/
> 
> Buildslave for this Build: yuzuki
> 
> Build Reason: The Nightly scheduler named 'nightly_virtfs' triggered this build
> Build Source Stamp: [branch for-upstream] HEAD
> Blamelist: 
> 
> BUILD FAILED: failed compile
> 
> sincerely,
>  -The Buildbot
> 

I am not sure whether others would be interested in the virtfs build
errors. This is a pre-integration tree so only VirtFS related changes
are pushed to this tree. May be virtfs build errors can only got to
aneesh.kumar@linux.vnet.ibm.com ?


-anesh

  reply	other threads:[~2012-01-29 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29  9:06 [Qemu-devel] buildbot failure in qemu on virtfs_x86_64_debian_6_0 qemu
2012-01-29 16:58 ` Aneesh Kumar K.V [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-06  8:27 qemu
2012-12-06 14:49 ` Aneesh Kumar K.V
2012-12-11  9:34   ` Stefan Hajnoczi
2012-12-11  9:49     ` 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=87k44amon3.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=gollub@b1-systems.de \
    --cc=lcapitulino@redhat.com \
    --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).