From: "Andreas Färber" <afaerber@suse.de>
To: Alex Bligh <alex@alex.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] peculiar make check problems: tests/libqtest.c
Date: Sun, 11 Aug 2013 16:22:05 +0200 [thread overview]
Message-ID: <52079E0D.5070702@suse.de> (raw)
In-Reply-To: <DEF7C9D97F9DED6CA81AC2A3@nimrod.local>
Hi,
Am 10.08.2013 13:20, schrieb Alex Bligh:
> Occasionally running make check I am seeing the following opaque error:
> ERROR:tests/libqtest.c:69:init_socket: assertion failed (ret != -1): (-1
> != -1)
>
> Rerunning it it runs clean. Any ideas?
Most likely a previous qtest will have failed, leaving temporary files
with that pid behind and your current test happens to get the same pid
again. Check /tmp/qtest*.
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-08-11 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 11:20 [Qemu-devel] peculiar make check problems: tests/libqtest.c Alex Bligh
2013-08-11 14:22 ` Andreas Färber [this message]
2013-08-11 14:52 ` Alex Bligh
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=52079E0D.5070702@suse.de \
--to=afaerber@suse.de \
--cc=alex@alex.org.uk \
--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).