qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: lcapitulino@redhat.com, gollub@b1-systems.de,
	qemu@buildbot.b1-systems.de, qemu-devel@nongnu.org,
	agraf@suse.de
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_i386_rhel61
Date: Tue, 15 May 2012 08:48:46 +0200	[thread overview]
Message-ID: <4FB1FC4E.6070407@redhat.com> (raw)
In-Reply-To: <4FB1AFF8.9090402@codemonkey.ws>

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

  parent reply	other threads:[~2012-05-15  6:49 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
2012-05-15  6:48   ` Gerd Hoffmann [this message]
  -- 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=4FB1FC4E.6070407@redhat.com \
    --to=kraxel@redhat.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=gollub@b1-systems.de \
    --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 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).