qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Buildbot failure: libqtest init_socket assertion failure
Date: Thu, 21 Nov 2013 09:42:53 +0100	[thread overview]
Message-ID: <20131121084253.GF27039@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <528CDDDA.6010304@suse.de>

On Wed, Nov 20, 2013 at 05:05:46PM +0100, Andreas Färber wrote:
> Am 20.11.2013 16:16, schrieb Stefan Hajnoczi:
> > On Wed, Nov 20, 2013 at 01:38:31PM +0100, Gerd Hoffmann wrote:
> >> On Mi, 2013-11-20 at 10:00 +0100, Stefan Hajnoczi wrote:
> >>> Hi Gerd,
> >>> make check is failing on kraxel_rhel61 due to the following:
> >>>
> >>> ERROR:tests/libqtest.c:71:init_socket: assertion failed (ret != -1): (-1 != -1)
> >>>
> >>> http://buildbot.b1-systems.de/qemu/builders/default_x86_64_rhel61/builds/782
> >>>
> >>> Can you investigate?  Perhaps there are stale files.
> >>
> >> Probably, that was the case when it happened last time.
> >>
> >> Yep, there are tons of /tmp/qtest-$number.{qmp,sock} files.  Cleared
> >> now.
> >>
> >> Where do they come from?  Running "make check" manually does _not_ leave
> >> stale files in /tmp for me.  Hmm.  What is going on?
> > 
> > Quite probably a resource leak in libqtest.  But I'm not sure which
> > scenario causes them to accumulate - maybe when a test assertion fails?
> 
> Yes, that's when it happens. I had wondered if adding some atexit() hook
> might be a solution but never found time to try that out.

Okay.  I'll investigate.

Stefan

      reply	other threads:[~2013-11-21  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20  9:00 [Qemu-devel] Buildbot failure: libqtest init_socket assertion failure Stefan Hajnoczi
2013-11-20 12:38 ` Gerd Hoffmann
2013-11-20 15:16   ` Stefan Hajnoczi
2013-11-20 16:05     ` Andreas Färber
2013-11-21  8:42       ` Stefan Hajnoczi [this message]

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=20131121084253.GF27039@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=afaerber@suse.de \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).