From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52461) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SU9nN-0006Pc-Ep for qemu-devel@nongnu.org; Tue, 15 May 2012 00:55:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SU9n9-0004Y4-9Y for qemu-devel@nongnu.org; Tue, 15 May 2012 00:55:37 -0400 Received: from mx1.b1-systems.de ([217.11.58.35]:53401) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SU9n9-0004Xm-34 for qemu-devel@nongnu.org; Tue, 15 May 2012 00:55:23 -0400 From: Daniel Gollub Date: Tue, 15 May 2012 06:55:11 +0200 Message-ID: <3695552.8UvdVNASJc@marvin.site> In-Reply-To: <4FB1AFF8.9090402@codemonkey.ws> References: <20120515010400.1A70D40397@buildbot.b1-systems.de> <4FB1AFF8.9090402@codemonkey.ws> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5174910.hIjX8dDSEc"; micalg="pgp-sha1"; protocol="application/pgp-signature" Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] buildbot failure in qemu on default_i386_rhel61 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, qemu@buildbot.b1-systems.de, agraf@suse.de, lcapitulino@redhat.com --nextPart5174910.hIjX8dDSEc Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" 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_rhe= l61 > > while building qemu.> > > Full details are available at: > > http://buildbot.b1-systems.de/qemu/builders/default_i386_rhel61/b= uilds/ > >263> > > Buildbot URL: http://buildbot.b1-systems.de/qemu/ > >=20 > > Buildslave for this Build: kraxel_rhel61_32bit > >=20 > > Build Reason: The Nightly scheduler named 'nightly_default' trigger= ed > > this build Build Source Stamp: [branch master] HEAD > > Blamelist: > >=20 > > BUILD FAILED: failed test > >=20 > > sincerely, > > > > -The Buildbot >=20 > 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=20 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=20= immeditally with f4f7d. The tests get aborted due to a timeout of the testsuite - they expire t= he 1200=20 seconds limit (buildslave testdriver is setting this limit). Before f4f= 7d the=20 default_s390 passed in approx. 9 seconds the testsuite. Since a lot of other slaves - but not all - timeout in the testsuite st= ep with=20 f4f7d there seems to be a infinite loop somehow or something blocking t= he=20 testsuite. Maybe the last testcase: check-qtest-sparc64 does not finish= in=20 time? Best Regards, Daniel --=20 Daniel Gollub Linux Consultant & Developer Tel.: +49-160 47 73 970=20 Mail: gollub@b1-systems.de B1 Systems GmbH Osterfeldstra=DFe 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 --nextPart5174910.hIjX8dDSEc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEABECAAYFAk+x4bYACgkQ7RS5XC+Mp42WtgCgkJYOVkl1EicWACbdtbWPNyu8 T0YAn30cMSjkDYcCNTnjtFMD79SRvf+g =Megi -----END PGP SIGNATURE----- --nextPart5174910.hIjX8dDSEc--