[Qemu-devel] buildbot failure in qemu on pci_i386_debian_5_0

[Qemu-devel] buildbot failure in qemu on pci_i386_debian_5_0

[qemu]

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

Buildbot URL: http://buildbot.b1-systems.de/qemu/

Buildslave for this Build: yuzuki

Build Reason: The Nightly scheduler named 'nightly_pci' triggered this build
Build Source Stamp: [branch pci] HEAD
Blamelist: 

BUILD FAILED: failed compile

sincerely,
 -The Buildbot

Re: [Qemu-devel] buildbot failure in qemu on pci_i386_debian_5_0

[Stefan Hajnoczi]

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

Re: [Qemu-devel] buildbot failure in qemu on pci_i386_debian_5_0

[Michael S. Tsirkin]

On Sat, Jun 11, 2011 at 02:34:59PM +0100, Stefan Hajnoczi wrote:
> 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

Fixed, thanks for the report!

Re: [Qemu-devel] buildbot failure in qemu on pci_i386_debian_5_0

[Peter Maydell]

On 11 June 2011 14:34, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> 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:

Is it possible to make the emails include the last 10 lines or
so of stdio for the failed stage? That would (usually) mean you
didn't have to bounce through the web pages to know what broke...

-- PMM

Re: [Qemu-devel] buildbot failure in qemu on pci_i386_debian_5_0

[Stefan Hajnoczi]

On Sun, Jun 12, 2011 at 9:26 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 11 June 2011 14:34, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> 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:
>
> Is it possible to make the emails include the last 10 lines or
> so of stdio for the failed stage? That would (usually) mean you
> didn't have to bounce through the web pages to know what broke...

Yes, but I think it requires writing a customer formatter function.
Here is the documentation including an example of a custom message
formatter:

http://buildbot.net/buildbot/docs/current/MailNotifier.html#MailNotifier

Perhaps someone has time to write the Python function that does what
Peter suggests?  As an additional customization it would be nice to
ignore git update errors since they are likely to be transient network
or git daemon issues - no email notifications need to be sent to the
mailing list.

Stefan