From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40067) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjAHr-0001ga-Ks for qemu-devel@nongnu.org; Wed, 20 Nov 2013 11:06:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VjAHl-0005Bx-QT for qemu-devel@nongnu.org; Wed, 20 Nov 2013 11:05:55 -0500 Received: from cantor2.suse.de ([195.135.220.15]:60850 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjAHl-0005Bn-KF for qemu-devel@nongnu.org; Wed, 20 Nov 2013 11:05:49 -0500 Message-ID: <528CDDDA.6010304@suse.de> Date: Wed, 20 Nov 2013 17:05:46 +0100 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <1384951111.2005.103.camel@nilsson.home.kraxel.org> <20131120151649.GB6012@stefanha-thinkpad.muc.redhat.com> In-Reply-To: <20131120151649.GB6012@stefanha-thinkpad.muc.redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Buildbot failure: libqtest init_socket assertion failure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi , Gerd Hoffmann Cc: qemu-devel 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 !=3D -1)= : (-1 !=3D -1) >>> >>> http://buildbot.b1-systems.de/qemu/builders/default_x86_64_rhel61/bui= lds/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_ lea= ve >> stale files in /tmp for me. Hmm. What is going on? >=20 > 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. Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg