From: Daniel Gollub <gollub@b1-systems.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, qemu@buildbot.b1-systems.de,
agraf@suse.de, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_i386_rhel61
Date: Tue, 15 May 2012 06:55:11 +0200 [thread overview]
Message-ID: <3695552.8UvdVNASJc@marvin.site> (raw)
In-Reply-To: <4FB1AFF8.9090402@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]
On Monday, May 14, 2012 08:23:04 PM Anthony Liguori wrote:
> On 05/14/2012 08:03 PM, qemu@buildbot.b1-systems.de wrote:
> > The Buildbot has detected a new failure on builder default_i386_rhel61
> > while building qemu.>
> > Full details are available at:
> > http://buildbot.b1-systems.de/qemu/builders/default_i386_rhel61/builds/
> >263>
> > Buildbot URL: http://buildbot.b1-systems.de/qemu/
> >
> > Buildslave for this Build: kraxel_rhel61_32bit
> >
> > Build Reason: The Nightly scheduler named 'nightly_default' triggered
> > this build Build Source Stamp: [branch master] HEAD
> > Blamelist:
> >
> > BUILD FAILED: failed test
> >
> > sincerely,
> >
> > -The Buildbot
>
> Did something change in buildbot recently? I'm having a hard time
> interpreting what's going on here.
Few weeks ago we introduced xen 4.0, xen 4.1 and xen-unstable buildbot-
factories / build-slaves. And the buildbot naster got restarted. But no other
changes I am aware of from buildbot master site ...
This one looks interesting:
http://buildbot.b1-systems.de/qemu/builders/default_s390
Test runs passed with 9f3484, 94d19 - at least tow times. And failed
immeditally with f4f7d.
The tests get aborted due to a timeout of the testsuite - they expire the 1200
seconds limit (buildslave testdriver is setting this limit). Before f4f7d the
default_s390 passed in approx. 9 seconds the testsuite.
Since a lot of other slaves - but not all - timeout in the testsuite step with
f4f7d there seems to be a infinite loop somehow or something blocking the
testsuite. Maybe the last testcase: check-qtest-sparc64 does not finish in
time?
Best Regards,
Daniel
--
Daniel Gollub
Linux Consultant & Developer
Tel.: +49-160 47 73 970
Mail: gollub@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-05-15 4:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 1:03 [Qemu-devel] buildbot failure in qemu on default_i386_rhel61 qemu
2012-05-15 1:23 ` Anthony Liguori
2012-05-15 4:55 ` Daniel Gollub [this message]
2012-05-15 6:48 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2013-01-11 22:06 qemu
2013-01-11 23:47 ` Andreas Färber
2013-01-12 0:40 ` Julien Grall
2012-10-04 23:49 qemu
2012-09-17 23:48 qemu
2012-09-13 23:47 qemu
2012-07-09 23:06 qemu
2012-07-02 23:43 qemu
2012-03-15 0:12 qemu
2012-02-04 0:06 qemu
2011-10-08 23:08 qemu
2011-10-03 23:13 qemu
2011-09-30 23:04 qemu
2011-08-29 23: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=3695552.8UvdVNASJc@marvin.site \
--to=gollub@b1-systems.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.