From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu-devel@nongnu.org
Cc: gollub@b1-systems.de, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] buildbot failure in qemu on pci_i386_debian_5_0
Date: Sat, 11 Jun 2011 14:34:59 +0100 [thread overview]
Message-ID: <BANLkTim4zACCLkVafCL1XyBLpQ3Q7E1CGw@mail.gmail.com> (raw)
In-Reply-To: <20110611022325.0634A3FC03@buildbot.b1-systems.de>
On Sat, Jun 11, 2011 at 3:23 AM, <qemu@buildbot.b1-systems.de> wrote:
> The Buildbot has detected a new failure on builder pci_i386_debian_5_0 while building qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/pci_i386_debian_5_0/builds/0
This is the first email notification from the QEMU buildbot, which
automatically builds qemu.git and several subsystem repositories (pci,
block, qmp, ppc, s390, agraf's xen, and trivial-patches). Builds run
every day and the goal is to catch build breakages before they enter
qemu.git.
To see the build errors relating to this failure, follow the link
above and select compile stdio output:
CC i386-softmmu/exec.o
/home/build/qemu/pci_i386_debian_5_0/build/exec.c: In function
'phys_page_for_each':
/home/build/qemu/pci_i386_debian_5_0/build/exec.c:1816: error: too few
arguments to function 'client->set_memory'
make[2]: *** [exec.o] Error 1
make[1]: *** [subdir-i386-softmmu] Error 2
This failure is in the pci tree, so I think Michael will investigate.
If you feel failure notifications are spamming the list, please let
Daniel Gollub <gollub@b1-systems.de> and me know so we can adjust
them.
For more info on the QEMU buildbot see:
http://wiki.qemu.org/ContinuousIntegration
http://buildbot.b1-systems.de/qemu/
Stefan
next prev parent reply other threads:[~2011-06-11 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 2:23 [Qemu-devel] buildbot failure in qemu on pci_i386_debian_5_0 qemu
2011-06-11 13:34 ` Stefan Hajnoczi [this message]
2011-06-12 7:34 ` Michael S. Tsirkin
2011-06-12 8:26 ` Peter Maydell
2011-06-12 12:56 ` Stefan Hajnoczi
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=BANLkTim4zACCLkVafCL1XyBLpQ3Q7E1CGw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=gollub@b1-systems.de \
--cc=mst@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).