From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:43304) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SUBZ5-00080k-Ah for qemu-devel@nongnu.org; Tue, 15 May 2012 02:49:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SUBZ3-0007cm-DB for qemu-devel@nongnu.org; Tue, 15 May 2012 02:48:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:19122) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SUBZ3-0007cd-58 for qemu-devel@nongnu.org; Tue, 15 May 2012 02:48:57 -0400 Message-ID: <4FB1FC4E.6070407@redhat.com> Date: Tue, 15 May 2012 08:48:46 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <20120515010400.1A70D40397@buildbot.b1-systems.de> <4FB1AFF8.9090402@codemonkey.ws> In-Reply-To: <4FB1AFF8.9090402@codemonkey.ws> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: lcapitulino@redhat.com, gollub@b1-systems.de, qemu@buildbot.b1-systems.de, qemu-devel@nongnu.org, agraf@suse.de On 05/15/12 03:23, 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. "make check" failure. GTESTER check-qtest-i386 GTESTER check-qtest-x86_64 GTESTER check-qtest-sparc GTESTER check-qtest-sparc64 command timed out: 1200 seconds without output, attempting to kill process killed by signal 9 program finished with exit code -1 Looks like check-qtest-sparc64 entered an endless loop ... cheers, Gerd