qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] test-aio-multithread assertion


From: Peter Maydell
Subject: Re: [Qemu-devel] test-aio-multithread assertion
Date: Thu, 5 Sep 2019 14:17:40 +0100

On Wed, 4 Sep 2019 at 12:50, Peter Maydell <address@hidden> wrote:
>
> Hi; I've been seeing intermittently on the BSDs this assertion
> running test-aio-multithread as part of 'make check':
>
> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}
> tests/test-aio-multithread -m=quick -k --tap < /dev/null |
> ./scripts/tap-drive
> r.pl --test-name="test-aio-multithread"
> PASS 1 test-aio-multithread /aio/multi/lifecycle
> PASS 2 test-aio-multithread /aio/multi/schedule
> ERROR - too few tests run (expected 5, got 2)
> Assertion failed: (!qemu_lockcnt_count(&ctx->list_lock)), function
> aio_ctx_finalize, file /home/qemu/qemu-test.kaRA0o/src/util/async.c,
> line 283.
> Abort trap (core dumped)
> gmake: *** [/home/qemu/qemu-test.kaRA0o/src/tests/Makefile.include:905:
> check-unit] Error 1
>
> Anybody got any ideas?

Here's a different intermittent assertion on Netbsd from test-aio-multithread:

MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}
tests/test-aio-multithread -m=quick
-k --tap < /dev/null | ./scripts/tap-driver.pl
--test-name="test-aio-multithread"
PASS 1 test-aio-multithread /aio/multi/lifecycle
PASS 2 test-aio-multithread /aio/multi/schedule
assertion "QSLIST_EMPTY(&ctx->scheduled_coroutines)" failed: file
"util/async.c", line 279, function "
aio_ctx_finalize"
ERROR - too few tests run (expected 5, got 2)

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]