Hi,
ERROR:/home/petmay01/linaro/qemu-for-merges/tests/libqtest.c:71:init_socket:
assertion failed (ret != -1): (-1 != -1)
FAIL
GTester: last random seed: R02S79ea313790bc9a8b21d9af5ed55c2fff
(pid=5080)
/i386/qom/pc:OK
On Fri, Jan 31, 2014 at 12:07:34AM +, Peter Maydell wrote:
On 21 November 2013 11:03, Stefan Hajnoczi stefa...@redhat.com wrote:
GLib uses abort(3) to exit failed test cases. As a result, the pid file and
UNIX domain sockets for a running test are leaked upon failure.
Since abort(3)
On 3 February 2014 09:54, Stefan Hajnoczi stefa...@redhat.com wrote:
I still think we should merge these patches :). Are you happy to merge
them?
They look like they're fixing a bug to me, so yes. You could
make my life easier by arranging for them to appear in a pull
request...
thanks
-- PMM
Am 03.02.2014 10:54, schrieb Stefan Hajnoczi:
On Fri, Jan 31, 2014 at 12:07:34AM +, Peter Maydell wrote:
On 21 November 2013 11:03, Stefan Hajnoczi stefa...@redhat.com wrote:
GLib uses abort(3) to exit failed test cases. As a result, the pid file and
UNIX domain sockets for a running test
On 3 February 2014 11:10, Andreas Färber afaer...@suse.de wrote:
As an explanation, the temporary files contain the PID. When they remain
behind due to test failure *and* the PID wraps around and file names
thus happen to match, the error was triggered, and thereby not on each
run but
On Mon, Feb 03, 2014 at 10:30:08AM +, Peter Maydell wrote:
On 3 February 2014 09:54, Stefan Hajnoczi stefa...@redhat.com wrote:
I still think we should merge these patches :). Are you happy to merge
them?
They look like they're fixing a bug to me, so yes. You could
make my life
On Fri, Jan 31, 2014 at 1:07 AM, Peter Maydell peter.mayd...@linaro.org wrote:
On 21 November 2013 11:03, Stefan Hajnoczi stefa...@redhat.com wrote:
GLib uses abort(3) to exit failed test cases. As a result, the pid file and
UNIX domain sockets for a running test are leaked upon failure.
On 21 November 2013 11:03, Stefan Hajnoczi stefa...@redhat.com wrote:
GLib uses abort(3) to exit failed test cases. As a result, the pid file and
UNIX domain sockets for a running test are leaked upon failure.
Since abort(3) does not call atexit(3) handler functions, we could set up a
Stefan Hajnoczi stefa...@redhat.com writes:
GLib uses abort(3) to exit failed test cases. As a result, the pid file and
UNIX domain sockets for a running test are leaked upon failure.
Since abort(3) does not call atexit(3) handler functions, we could set up a
SIGABRT handler that performs
On Thu, Nov 21, 2013 at 12:03:53PM +0100, Stefan Hajnoczi wrote:
GLib uses abort(3) to exit failed test cases. As a result, the pid file and
UNIX domain sockets for a running test are leaked upon failure.
Since abort(3) does not call atexit(3) handler functions, we could set up a
SIGABRT
GLib uses abort(3) to exit failed test cases. As a result, the pid file and
UNIX domain sockets for a running test are leaked upon failure.
Since abort(3) does not call atexit(3) handler functions, we could set up a
SIGABRT handler that performs cleanup. But there are other conditions where
11 matches
Mail list logo
